Hi all,
OK, the votes are in and it looks like the least-bad time for meetings right now are 14:00 UTC on Thursdays. I think we were missing a few votes, though, so I hope this time will work for the most people.
Please send me any agenda items by Monday afternoon and I will send out a meeting reminder then.
Thanks,
jzb
On Fri, Mar 07, 2014 at 01:10:58PM -0600, Joe Brockmeier wrote:
OK, the votes are in and it looks like the least-bad time for meetings right now are 14:00 UTC on Thursdays. I think we were missing a few votes, though, so I hope this time will work for the most people. Please send me any agenda items by Monday afternoon and I will send out a meeting reminder then.
Let's add "Replace cloud-init with min-metadata-service as the default; provide separate cloud-init enabled image".
This would be contingent on min-metadata-service implementing a bit more basic functionality (execute userdata scripts, option to create and use "fedora" user, and GCE support). Additionally, it would be nice to start building up a very simple library of #! user-data scripts that do the basic things people want to do (e.g., install and enable some services, install puppet and hand off, and also whatever Heat needs).
On Fri, 2014-03-07 at 15:17 -0500, Matthew Miller wrote:
On Fri, Mar 07, 2014 at 01:10:58PM -0600, Joe Brockmeier wrote:
OK, the votes are in and it looks like the least-bad time for meetings right now are 14:00 UTC on Thursdays. I think we were missing a few votes, though, so I hope this time will work for the most people. Please send me any agenda items by Monday afternoon and I will send out a meeting reminder then.
Let's add "Replace cloud-init with min-metadata-service as the default; provide separate cloud-init enabled image".
Thanks!
Any other agenda items?
Best,
jzb
On Sat, Mar 8, 2014 at 5:17 AM, Matthew Miller mattdm@fedoraproject.org wrote:
On Fri, Mar 07, 2014 at 01:10:58PM -0600, Joe Brockmeier wrote:
OK, the votes are in and it looks like the least-bad time for meetings right now are 14:00 UTC on Thursdays. I think we were missing a few votes, though, so I hope this time will work for the most people. Please send me any agenda items by Monday afternoon and I will send out a meeting reminder then.
Let's add "Replace cloud-init with min-metadata-service as the default; provide separate cloud-init enabled image".
Since Matt just brought that up in another thread and I think it might be my new favorite option (only just had a very quick look at the github page), let's add CoreOS's cloud-init [1] to this discussion. It's written in Go and supports a subset of what cloud-init does plus additions to control etcd [2] and fleet [3] which are tools that I think we want to have at least on the Docker Host image, anyway.
-- Sandro
[1] https://github.com/coreos/coreos-cloudinit [2] https://coreos.com/using-coreos/etcd/ [3] https://github.com/coreos/fleet
This would be contingent on min-metadata-service implementing a bit more basic functionality (execute userdata scripts, option to create and use "fedora" user, and GCE support). Additionally, it would be nice to start building up a very simple library of #! user-data scripts that do the basic things people want to do (e.g., install and enable some services, install puppet and hand off, and also whatever Heat needs).
-- Matthew Miller -- Fedora Project -- mattdm@fedoraproject.org _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Sat, Mar 8, 2014 at 4:10 AM, Joe Brockmeier jzb@redhat.com wrote:
Hi all,
OK, the votes are in and it looks like the least-bad time for meetings right now are 14:00 UTC on Thursdays. I think we were missing a few votes, though, so I hope this time will work for the most people.
Please send me any agenda items by Monday afternoon and I will send out a meeting reminder then.
Well, that's 11 PM for me, with school the next morning - so I will sometimes be able to make it and sometimes not.
Things I'd like to be discussed: - Do we want the Docker Host image to use ostree (as kinda yum/dnf replacement)? - Do we want to (try and) kick out Python on the Docker Host image? This would *require* both replacing cloud-init by min-metadata-service and yum by ostree. - How can we get the community more involved in our efforts? Changes need owners.
-- Sandro
On Sat, Mar 08, 2014 at 09:43:21AM +0900, Sandro red Mathys wrote:
Well, that's 11 PM for me, with school the next morning - so I will sometimes be able to make it and sometimes not.
We'll try to make good minutes with liberal #infos, and also to make sure we have list-based discussion like this too too.
- Do we want to (try and) kick out Python on the Docker Host image?
This would *require* both replacing cloud-init by min-metadata-service and yum by ostree.
I'd love to try.
- How can we get the community more involved in our efforts? Changes
need owners.
*nod*
----- Original Message -----
From: "Matthew Miller" mattdm@fedoraproject.org To: "Fedora Cloud SIG" cloud@lists.fedoraproject.org Sent: Saturday, March 8, 2014 7:04:04 AM Subject: Re: New meeting time + call for agenda items
On Sat, Mar 08, 2014 at 09:43:21AM +0900, Sandro red Mathys wrote:
Well, that's 11 PM for me, with school the next morning - so I will sometimes be able to make it and sometimes not.
We'll try to make good minutes with liberal #infos, and also to make sure we have list-based discussion like this too too.
- Do we want to (try and) kick out Python on the Docker Host image?
This would *require* both replacing cloud-init by min-metadata-service and yum by ostree.
I'd love to try.
+1.
The one concern I have about this is that both are relatively young projects (particularly the former) and will need lots of time + effort put into getting them into complete enough shape for production usage. We are a pretty small group of people with lots on our agenda for the next 6-7 months (until F21) and these are two components that *have* to work. It might make sense to target getting rid of python for F22 and choose either ostree or min-metadata-service to replace yum or cloud-init in the F21 cycle.
-s
- How can we get the community more involved in our efforts? Changes
need owners.
*nod*
-- Matthew Miller -- Fedora Project -- mattdm@fedoraproject.org _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Sat, Mar 8, 2014 at 5:46 PM, Sam Kottler skottler@redhat.com wrote:
----- Original Message -----
From: "Matthew Miller" mattdm@fedoraproject.org To: "Fedora Cloud SIG" cloud@lists.fedoraproject.org Sent: Saturday, March 8, 2014 7:04:04 AM Subject: Re: New meeting time + call for agenda items
On Sat, Mar 08, 2014 at 09:43:21AM +0900, Sandro red Mathys wrote:
Well, that's 11 PM for me, with school the next morning - so I will sometimes be able to make it and sometimes not.
We'll try to make good minutes with liberal #infos, and also to make sure we have list-based discussion like this too too.
- Do we want to (try and) kick out Python on the Docker Host image?
This would *require* both replacing cloud-init by min-metadata-service and yum by ostree.
I'd love to try.
+1.
The one concern I have about this is that both are relatively young projects (particularly the former) and will need lots of time + effort put into getting them into complete enough shape for production usage. We are a pretty small group of people with lots on our agenda for the next 6-7 months (until F21) and these are two components that *have* to work. It might make sense to target getting rid of python for F22 and choose either ostree or min-metadata-service to replace yum or cloud-init in the F21 cycle.
Well, those concerns are valid. But I'd rather give it a try and fail than run away and hide in fear without even looking at it first. As soon as I have some kind of access to some kind of cloud (without charging my credit card), I'll play around with the various bits (and some other ideas that I want to try out) a bit. I tend to think it's doable without a huge effort. Less effort than most changes require, anyway. Also, I do have a couple of hours every week to work on this and other changes so I hope to help with a couple of changes nevertheless.
-- Sandro
-s
- How can we get the community more involved in our efforts? Changes
need owners.
*nod*
-- Matthew Miller -- Fedora Project -- mattdm@fedoraproject.org _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Sat, Mar 08, 2014 at 08:51:51PM +0900, Sandro red Mathys wrote:
than run away and hide in fear without even looking at it first. As soon as I have some kind of access to some kind of cloud (without charging my credit card), I'll play around with the various bits (and
We should be able to get you access to Fedora's own openstack instance for working on this -- file a ticket with Fedora Infrastructure, I think.
On Mon, Mar 10, 2014 at 2:46 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Sat, Mar 08, 2014 at 08:51:51PM +0900, Sandro red Mathys wrote:
than run away and hide in fear without even looking at it first. As soon as I have some kind of access to some kind of cloud (without charging my credit card), I'll play around with the various bits (and
We should be able to get you access to Fedora's own openstack instance for working on this -- file a ticket with Fedora Infrastructure, I think.
Or you can try my pet project: https://github.com/juergh/dwarf/ which adds the OpenStack API (a subset of it, that is) ontop of your your locally running libvirt daemon. It'll allow you to use the standard OpenStack python clients to manage VMs and cloud images on your local machine. I use it to test images before uploading them to the (HP) cloud, so it's slightly biased towards our OpenStack implementation. It also provides an EC2 metadata service to the instance to please cloud-init (but no OpenStack config drive). Feedback, bug reports and patches are more than welcome.
Sorry, no RPMs yet.
...Juerg
-- Matthew Miller -- Fedora Project -- mattdm@fedoraproject.org _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Mon, Mar 10, 2014 at 10:59 PM, Juerg Haefliger juergh@gmail.com wrote:
On Mon, Mar 10, 2014 at 2:46 PM, Matthew Miller mattdm@fedoraproject.org wrote:
On Sat, Mar 08, 2014 at 08:51:51PM +0900, Sandro red Mathys wrote:
than run away and hide in fear without even looking at it first. As soon as I have some kind of access to some kind of cloud (without charging my credit card), I'll play around with the various bits (and
We should be able to get you access to Fedora's own openstack instance for working on this -- file a ticket with Fedora Infrastructure, I think.
Will do, thanks.
Or you can try my pet project: https://github.com/juergh/dwarf/ which adds the OpenStack API (a subset of it, that is) ontop of your your locally running libvirt daemon. It'll allow you to use the standard OpenStack python clients to manage VMs and cloud images on your local machine. I use it to test images before uploading them to the (HP) cloud, so it's slightly biased towards our OpenStack implementation. It also provides an EC2 metadata service to the instance to please cloud-init (but no OpenStack config drive). Feedback, bug reports and patches are more than welcome.
I did stumble over that before already and I do want to look into it, but I was kinda hoping...
Sorry, no RPMs yet.
...that RPMs would show up before I do ;) At least on Copr? :)
...Juerg
-- Matthew Miller -- Fedora Project -- mattdm@fedoraproject.org _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Mon, Mar 10, 2014 at 3:03 PM, Sandro "red" Mathys red@fedoraproject.org wrote:
On Mon, Mar 10, 2014 at 10:59 PM, Juerg Haefliger juergh@gmail.com
wrote:
On Mon, Mar 10, 2014 at 2:46 PM, Matthew Miller <
mattdm@fedoraproject.org>
wrote:
On Sat, Mar 08, 2014 at 08:51:51PM +0900, Sandro red Mathys wrote:
than run away and hide in fear without even looking at it first. As soon as I have some kind of access to some kind of cloud (without charging my credit card), I'll play around with the various bits (and
We should be able to get you access to Fedora's own openstack instance
for
working on this -- file a ticket with Fedora Infrastructure, I think.
Will do, thanks.
Or you can try my pet project: https://github.com/juergh/dwarf/ which
adds
the OpenStack API (a subset of it, that is) ontop of your your locally running libvirt daemon. It'll allow you to use the standard OpenStack
python
clients to manage VMs and cloud images on your local machine. I use it
to
test images before uploading them to the (HP) cloud, so it's slightly
biased
towards our OpenStack implementation. It also provides an EC2 metadata service to the instance to please cloud-init (but no OpenStack config drive). Feedback, bug reports and patches are more than welcome.
I did stumble over that before already and I do want to look into it, but I was kinda hoping...
Sorry, no RPMs yet.
...that RPMs would show up before I do ;)
Maeh :-)
At least on Copr? :)
Hmm... Ok. Just google'd copr. I'll see what I can do...
...Juerg
Hi,
As for the new meeting time, I'll do my best. I won't be able to commit myself to work on new features for a while, as I'm looking actively for a new position that doesn't require me to relocate and without ethical issues.
regards, H.
On Mon, Mar 10, 2014 at 02:59:24PM +0100, Juerg Haefliger wrote:
Or you can try my pet project: https://github.com/juergh/dwarf/ which adds the OpenStack API (a subset of it, that is) ontop of your your locally running libvirt daemon. It'll allow you to use the standard OpenStack python clients to manage VMs and cloud images on your local machine. I use it to test images before uploading them to the (HP) cloud, so it's slightly biased towards our OpenStack implementation. It also provides an EC2 metadata service to the instance to please cloud-init (but no OpenStack config drive). Feedback, bug reports and patches are more than welcome.
Juerg, this is neat! Thanks for sharing!
On Sat, Mar 8, 2014 at 4:10 AM, Joe Brockmeier jzb@redhat.com wrote:
Hi all,
OK, the votes are in and it looks like the least-bad time for meetings right now are 14:00 UTC on Thursdays. I think we were missing a few votes, though, so I hope this time will work for the most people.
FYI, I changed the Cloud SIG, Cloud WG and Meeting channel wiki pages to reflect our new time.Note that we also change from #fedora-meeting-1 to #fedora-meeting at the same time.
-- Sandro
Please send me any agenda items by Monday afternoon and I will send out a meeting reminder then.
Thanks,
jzb
Joe Brockmeier | Principal Cloud & Storage Analyst jzb@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Fri, 2014-03-07 at 13:10 -0600, Joe Brockmeier wrote:
Hi all,
OK, the votes are in and it looks like the least-bad time for meetings right now are 14:00 UTC on Thursdays. I think we were missing a few votes, though, so I hope this time will work for the most people.
Given no objections to this time, I figured I would send this out to avoid confusion:
2014-03-13 07:00 Thu US/Pacific PDT 2014-03-13 10:00 Thu US/Eastern EDT 2014-03-13 14:00 Thu UTC <- 2014-03-13 14:00 Thu Europe/London <- 2014-03-13 15:00 Thu Europe/Paris CET 2014-03-13 15:00 Thu Europe/Berlin CET 2014-03-13 19:30 Thu Asia/Calcutta IST 2014-03-13 22:00 Thu Asia/Singapore SGT 2014-03-13 22:00 Thu Asia/Hong_Kong HKT 2014-03-13 23:00 Thu Asia/Tokyo JST ------------------new day---------------------- 2014-03-14 00:00 Fri Australia/Brisbane EST