Re: EC2 access for testing?
by Geoffrey Marr
Yeah, you get 750 hours per month total for free, within the confines of
the small amount of disk, RAM, and bandwidth you get. I always make sure to
terminate any machines I spin up once I'm done testing so I don't get
charged for going over that (which is hard to do, you have to run multiple
machines). There's also a bandwidth cap, I think it's around 20gb total,
then you start getting charged. 20gb is more than enough when running the
five tests we have that are blocking for cloud; as long as the machines are
terminated once tested, it's really hard to have an overage.
Geoff Marr
IRC: coremodule
On Fri, Sep 13, 2019 at 7:49 PM Adam Williamson <adamwill(a)fedoraproject.org>
wrote:
> On Fri, 2019-09-13 at 16:02 -0600, Geoffrey Marr wrote:
> > I have been using Amazon's "Free Tier" cloud machines to test EC2 images
> > since 2016. Anyone with an Amazon account (which is free) can spin up a
> > "free tier" machine to run the tests on. With access so easy, is it
> > Fedora's job to provide users/testers with an account with which to test
> > these images?
>
> There are limits on that, right? If you use more than the limits you
> get charged?
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> _______________________________________________
> cloud mailing list -- cloud(a)lists.fedoraproject.org
> To unsubscribe send an email to cloud-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org
>
4 years, 7 months
Re: EC2 access for testing?
by Dusty Mabe
On 9/13/19 4:51 PM, Adam Williamson wrote:
> On Fri, 2019-09-13 at 16:25 -0400, Dusty Mabe wrote:
>>
>> On 9/13/19 3:44 PM, Adam Williamson wrote:
>>> Hi folks! We're currently still discussing adjusting the release
>>> criteria to explicitly require Fedora releases to boot in EC2. Someone
>>> pointed out that if we're going to require that, it would be good if we
>>> had an account allowing EC2 access for testing, so individual Fedora
>>> testers don't have to potentially pay out-of-pocket just to test Fedora
>>> works in EC2. Does anyone know if we have an existing arrangement with
>>> Amazon for this? Thanks!
>>>
>>
>> cc Paul Frields
>>
>> I have access to an account I think we use explicitly for testing Fedora in AWS.
>> Adam, if Paul doesn't point out any reason not to I can hand you some credentials.
>
> It'd be better for it to be something more robust and 'team-accessible'
> than just people emailing each other passwords, ideally :)
>
Encrypted of course :-P
It would be better to have it be something more managed but I don't have anything
more robust that I can offer right now. Maybe fedora infra does.
Dusty
4 years, 7 months
Re: EC2 access for testing?
by Dusty Mabe
On 9/13/19 3:44 PM, Adam Williamson wrote:
> Hi folks! We're currently still discussing adjusting the release
> criteria to explicitly require Fedora releases to boot in EC2. Someone
> pointed out that if we're going to require that, it would be good if we
> had an account allowing EC2 access for testing, so individual Fedora
> testers don't have to potentially pay out-of-pocket just to test Fedora
> works in EC2. Does anyone know if we have an existing arrangement with
> Amazon for this? Thanks!
>
cc Paul Frields
I have access to an account I think we use explicitly for testing Fedora in AWS.
Adam, if Paul doesn't point out any reason not to I can hand you some credentials.
Dusty
4 years, 7 months
Fedora CoreOS Meeting Minutes 2019-09-11
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-11/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-11/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-11/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:31:02 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-11/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:31:06)
* Action items from last meeting (dustymabe, 16:35:10)
* Ignition: Support multi part mime for user-data (dustymabe, 16:35:53)
* LINK: https://github.com/coreos/ignition/issues/849 (dustymabe,
16:36:01)
* will punt on discussing coreos/ignition/issues/849 until next week
when ajeddeloh is back (dustymabe, 16:39:00)
* coreos/toolbox v2 (dustymabe, 16:39:11)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/38
(dustymabe, 16:39:21)
* we want to ship something like toolbox and toolbox is something that
already exists so we will ship it once we've iterated on the
dependencies in #38. Will work with debarshiray to see if there is
an updated rpm we can evaluate. (dustymabe, 16:49:12)
* docker group or not (dustymabe, 16:51:25)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/2
(dustymabe, 16:51:36)
* we are going to try to prioritize systemd-sysusers work for FCOS
stable, but we will hackishly try to add docker to the /etc/group
file to smooth the path for users who are currently using FCOS
preview releases (dustymabe, 17:06:48)
* Allow creation of immutable directories below root folder (dustymabe,
17:07:40)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/270
(dustymabe, 17:07:49)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/270
(dustymabe, 17:13:34)
* LINK:
https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject....
(dustymabe, 17:17:10)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/159
(bgilbert, 17:18:11)
* ACTION: bgilbert to update #159 to add doc item for immutable '/'
(dustymabe, 17:19:37)
* while having an immutable top level directory seems like a
reasonable ask there are technical reasons why this won't work for
fedora coreos and we suggest users to change their mount point to be
under one of the writable filesystems (dustymabe, 17:20:43)
* open floor (dustymabe, 17:22:30)
Meeting ended at 17:30:41 UTC.
Action Items
------------
* bgilbert to update #159 to add doc item for immutable '/'
Action Items, by person
-----------------------
* bgilbert
* bgilbert to update #159 to add doc item for immutable '/'
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (117)
* bgilbert (54)
* jlebon (28)
* zodbot (17)
* kaeso[m] (12)
* red_beard (2)
* walters (2)
* slowrie (1)
* lorbus (1)
* mnguyen_ (1)
* geoff- (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
4 years, 7 months
mount to folder below root fails
by Heiko Onnebrink
I am testing migration of CoreOS with Ignition 2.2 (named here current env) to to preview FedoraCoreOS with Ignition 3.0 (named here new env)
Tests are performed on OpenStack Rocky on prem.
In current env we mount /dev/vdb to a folder /dockerdata and /dev/vdc to /var/lib/docker which works fine using Ignition 2.0.
I have transferred config to Ignition 3 and test now in new env.
Mount to /var/lib/docker is fine, mount to /dockerdata fails :
..
[ 9.931065] ignition[696]: "filesystems": [
[ 9.931075] ignition[696]: {
[ 9.931087] ignition[696]: "device": "/dev/vdc",
[ 9.931097] ignition[696]: "format": "ext4",
[ 9.931107] ignition[696]: "label": "docker",
[ 9.932644] ignition[696]: "path": "/var/lib/docker",
[ 9.932660] ignition[696]: "wipeFilesystem": true
[ 9.932670] ignition[696]: },
[ 9.932680] ignition[696]: {
[ 9.932689] ignition[696]: "device": "/dev/vdb",
[ 9.932699] ignition[696]: "format": "ext4",
[ 9.932714] ignition[696]: "label": "dockerdata",
[ 9.932724] ignition[696]: "path": "/dockerdata",
[ 9.932734] ignition[696]: "wipeFilesystem": true
[ 9.932743] ignition[696]: }
[ 9.932753] ignition[696]: ]
..
..
[ 9.935087] ignition[696]: }CRITICAL : Ignition failed: mkdir /sysroot/dockerdata: operation not permitted
[ 9.936383] umount[704]: umount: /sysroot/var: not mounted.
[ 9.936548] systemd[1]: ignition-mount.service: Main process exited, code=exited, status=1/FAILURE
[ 9.936696] systemd[1]: ignition-mount.service: Failed with result 'exit-code'.
[ 9.936730] systemd[1]: Failed to start Ignition (mount).
Also tried to explicitly add a create directory /dockerdata using Ignition "directories .. /dockerdata" but same error.
[ 9.537684] ignition[696]: }CRITICAL : Ignition failed: mkdir /sysroot/dockerdata: operation not permitted
Did I do something in the past that is not ok but was "tolerated" and now fails due to more strict checking?
Thanks for any feedback
cheers
Heiko
4 years, 7 months
Fedora CoreOS meeting canceled for 2019-09-04
by Benjamin Gilbert
Hi all,
Since there are no fedora-coreos-tracker tickets with the `meeting` label,
the Fedora CoreOS IRC meeting for 2019-09-04 is canceled.
Sincerely,
--meeting canceler shell script
4 years, 7 months