Re: [Openstack-operators] [openstack-dev] mod_wsgi: what services are people using with it?
On 08/17/2016 03:22 PM, Nick Papadonis wrote: > Hi Folks, > > I was hacking in this area on Mitaka and enabled Glance, Cinder, Heat, > Swift, Ironic, Horizon and Keystone under Apache mod_wsgi instead of the > Eventlet server.Cinder, Keystone, Heat and Ironic provide Python > source in Github to easily enable this. It appears that Glance and > Swift (despite the existence of > https://github.com/openstack/swift/blob/2bf5eb775fe3ad6d3a2afddfc7572318e85d10be/doc/source/apache_deployment_guide.rst) > provide no such Python source to call from the Apache conf file. > > That said, is anyone using Glance, Swift, Neutron or Nova (marked > experimental) in production environments with mod_wsgi? I had to put > together code to launch a subset of these which does not appear > integrated in Github. Appreciate your insight. > > Thanks, > Nick > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > This might be better for the ops list, so cc'd them. I don't use apache / mod_wsgi, but I do use uwsgi with cinder, horizon, keystone, neutron and nova. At the moment it's just glance that's not using it, but there was a bug iirc with how it interacted with uwsgi. I should look into it again. I even made a blog post about it a while back. https://mthode.org/posts/2016/Mar/of-openstack-and-uwsgi/ -- -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Ops MidCycle Registration
My guess would be either processing fees or taxes (or both). On 07/14/2016 05:25 PM, Matt Fischer wrote: > Thanks Erin. I did this just now and it charged me $22.09. Not a big > deal, but what's the extra? Taxes? > > > On Jul 14, 2016 3:43 PM, "Erin Disney" <mailto:e...@openstack.org>> wrote: > > All- > > Thank you for your patience as we finalized details for the Ops > MidCycle in New York this August. If you plan to attend, please RSVP > here: https://opsmidcyclenyc2016.eventbrite.com > > Please note that the cost of the event is $20 USD. If you are > needing assistance with visas or have any other questions about the > event, please contact me directly. > > Thanks! > > Erin Disney > OpenStack Marketing > e...@openstack.org <mailto:e...@openstack.org> > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > <mailto:OpenStack-operators@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Moving from distro packages to containers (or virtualenvs...)
On 05/13/2016 01:59 PM, Joshua Harlow wrote: > Matthew Thode wrote: >> On 05/13/2016 12:48 PM, Joshua Harlow wrote: >>>>> * Was/is kolla used or looked into? or something custom? >>>>> >>>> Openstack-ansible, which is Openstack big-tent. It used to be >>>> os-ansible-deployment in stackforge, but we've removed the >>>> rackspacisms. >>>>I will say that openstack-ansible is one of the few that have been >>>> doing upgrades reliably for a while, since at least Icehouse, maybe >>>> further. >>> Whats the connection between 'openstack-ansible' and 'kolla', is there >>> any (or any in progress?) >>> >> >> The main difference is that openstack-ansible uses more heavy weight >> containers from a common base (ubuntu 14.04 currently, 16.04/cent >> 'soon'), it then builds on top of that, uses python virtualenvs as well. >> Kolla on the other hand creates the container images centrally and >> ships them around. > > So I guess its like the following (correct me if I am wrong): > > openstack-ansible > - > > 1. Sets up LXC containers from common base on deployment hosts (ansible > here to do this) > 2. Installs things into those containers (virtualenvs, packages, git > repos, other ... more ansible) > 3. Connects all the things together (more more ansible). > 4. Decommissions existing container (if it exists) and replaces with new > container (more more more ansible). > 5. <> > More or less, we do in place upgrades, so long lived containers, but could just as easily destroy and replace. > kolla > - > > 1. Builds up (installing things and such) *docker* containers outside of > deployment hosts (say inside jenkins) [not ansible] > 2. Ships built up containers to *a* docker hub > 3. Ansible then runs commands on deployment hosts to download image from > docker hub > 4. Connects all the things together (more ansible). > 5. Decommissions existing container (if it exists) and replaces with new > container (more more ansible). > 6. <> > > Yes the above is highly simplistic, but just trying to get a feel for > the different base steps here ;) > I think so? not sure as I don't work with kolla >> >> The other thing to note is that Kolla has not done a non-greenfield >> upgrade as far as I know, I know it's on their roadmap though. >> -- -- Matthew Thode (prometheanfire) ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Moving from distro packages to containers (or virtualenvs...)
On 05/13/2016 12:48 PM, Joshua Harlow wrote: >>> * Was/is kolla used or looked into? or something custom? >>> >> >> Openstack-ansible, which is Openstack big-tent. It used to be >> os-ansible-deployment in stackforge, but we've removed the rackspacisms. >> I will say that openstack-ansible is one of the few that have been >> doing upgrades reliably for a while, since at least Icehouse, maybe >> further. > > Whats the connection between 'openstack-ansible' and 'kolla', is there > any (or any in progress?) > The main difference is that openstack-ansible uses more heavy weight containers from a common base (ubuntu 14.04 currently, 16.04/cent 'soon'), it then builds on top of that, uses python virtualenvs as well. Kolla on the other hand creates the container images centrally and ships them around. The other thing to note is that Kolla has not done a non-greenfield upgrade as far as I know, I know it's on their roadmap though. -- -- Matthew Thode (prometheanfire) ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Moving from distro packages to containers (or virtualenvs...)
On 05/12/2016 04:04 PM, Joshua Harlow wrote: > Hi there all-ye-operators, > > I am investigating how to help move godaddy from rpms to a > container-like solution (virtualenvs, lxc, or docker...) and a set of > questions that comes up is the following (and I would think that some > folks on this mailing list may have some useful insight into the answers): > > * Have you done the transition? > We've been using openstack-ansible since it existed, it's working well for us. > * How did the transition go? > It can be painful, but it's worked out in the long run. > * Was/is kolla used or looked into? or something custom? > Openstack-ansible, which is Openstack big-tent. It used to be os-ansible-deployment in stackforge, but we've removed the rackspacisms. I will say that openstack-ansible is one of the few that have been doing upgrades reliably for a while, since at least Icehouse, maybe further. > * How long did it take to do the transition from a package based > solution (with say puppet/chef being used to deploy these packages)? > > * Follow-up being how big was the team to do this? Our team was somewhat bigger than most as we have many deployments and we had to do it from scratch. If you CAN do it solo, but I'd recommend you have coverage / on call for whatever your requirements are. > > * What was the roll-out strategy to achieve the final container solution? > For Openstack-ansible I'd recommend deploying a service at a time, migrating piecemeal. You can migrate to the same release as you are on (I hope), though I'd recommend kilo or greater as upgrades can get annoying after a while. > Any other feedback (and/or questions that I missed)? > > Thanks, > > Josh > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- -- Matthew Thode (prometheanfire) ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Tokyo - Infra containers session
I just got done updating the etherpad with my battleplan for the session, feel free to add anything else, but keep in mind it is just 40 minutes and nothing survives contact with the enemy, or the user I suppose... https://etherpad.openstack.org/p/TYO-ops-infrastructure-containers And here's the logistical info if you want to attend :P http://mitakadesignsummit.sched.org/event/0382eb53976eae78b1bd820a27fadf8b Wednesday October 28, 2015 11:15am - 11:55am Suzuran room - building 4 floor 2 (grand prince hotel takanawa) -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Draft Agenda for PAO Ops Meetup (August 18, 19)
ropose to slot in instead one of these three, which are >>> currently not well included on the agenda: >>> >>> 1) apps.openstack.org - What the Ops Community would like from it, >>> should we look from the Application side, ie Applications that can run >>> on your cloud, or Augment your cloud, Products that can help enhance >>> your cloud. >>> >>> 2) Openstack Personas (validation) - The UX team will have a set of >>> roles that we would like to validate with the opertator community. >>> >>> 3) Task Taxonomy - The UX team is creating an inventory of >>> "standardized" tasks that can be used to create scenarios and create a >>> common vernacular within the community. >>> >>> Any thoughts? >>> >>> Regards, >>> >>> >>> Tom >>> >>> On 03/08/15 18:48, Tom Fifield wrote: >>>> Hi all, >>>> >>>> Registrations are going well for our meetup in Palo Alto. If you're >>>> on the fence, hopefully this discussion will get you quickly over the >>>> line so you don't miss out! >>>> >>>> http://www.eventbrite.com/e/openstack-ops-mid-cycle-meetup-tickets-17703258924 >>>> >>>> >>>> So, I've taken our suggestions and attempted to wrangle them into >>>> something that would fit in the space we have over 2 days. >>>> >>>> As a reminder, we have two different kind of sessions - General >>>> Sessions, which are discussions for the operator community aimed to >>>> produce actions (eg best practices, feedback on badness), >>>> and**Working groups**focus on specific topics aiming to make concrete >>>> progress on tasks in that area. >>>> >>>> As always, some stuff has been munged and mangled in an attempt to >>>> fit it in. For example, we'd expect to talk about Kolla more >>>> generally in the context of "Using Containers for Deployment", >>>> because there are some other ways to do that too. Similarly, we'd >>>> expect the "ops project" discussion to be rolled into the session on >>>> the user committee. >>>> >>>> Anyway, take a look at the below and reply with your comments! Is >>>> anything missing? Something look like a terrible idea? Want to >>>> completely change the room layout? There's still a little bit of >>>> flexibility at this stage. >>>> >>>> >>>> >>>> Tuesday Med II Med III Salon A Salon B Bacchus >>>> 9:00 - 10:00 Registration >>>> >>>> >>>> >>>> 10:00 - 10:30 Introduction >>>> >>>> >>>> >>>> 10:30 - 11:15 Burning Issues >>>> >>>> >>>> >>>> 11:15 - 11:55 Hypervisor Tuning >>>> >>>> >>>> >>>> 11:55 - 12:05 Breakout Explain >>>> >>>> >>>> >>>> 12:05 - 13:30 Lunch >>>> >>>> >>>> >>>> 13:30 - 15:00 Large Deployments Team Burning Issues >>>> Logging WG >>>> Upgrades WG Ops Guide Fixing >>>> 15:00 - 15:30 Coffee >>>> >>>> >>>> >>>> 15:30 - 16:00 Breakout Reports >>>> >>>> >>>> >>>> 16:00 - 17:00 Using Containers for Deployment >>>> >>>> >>>> >>>> 17:00 - 18:00 Lightening Talks >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Wednesday Med II Med III Salon A Salon B Bacchus >>>> 9:00 - 09:45 CMDB: use cases >>>> >>>> >>>> >>>> 9:45 - 10:30 Deployment Tips - read only slaves? admin-only API >>>> servers? >>>> >>>> >>>> >>>> 10:30 - 11:15 What network model are you using? Are you happy? >>>> >>>> >>>> >>>> 11:15 - 11:30 Coffee >>>> >>>> >>>> >>>> 11:30 - 12:15 User Committee Discussion >>>> >>>> >>>> >>>> 12:15 - 12:20 Breakout Explain >>>> >>>> >>>> >>>> 12:20 - 13:30 Lunch >>>> >>>> >>>> >>>> 13:30 - 15:00 Tools and Monitoring Product WG >>>> Packaging HPC >>>> Working Group Ops Tags Team >>>> 15:00 - 15:30 Coffee >>>> >>>> >>>> >>>> 15:30 - 16:00 Breakout Reports >>>> >>>> >>>> >>>> 16:00 - 17:00 Feedback Session, Tokyo Planning >>>> >>>> >>>> >>>> >>>> >>>> >>>> There will be a followup email shortly regarding moderators for the >>>> sessions - thanks to those who volunteered so far! >>>> >>>> >>>> Regards, >>>> >>>> >>>> Tom >>>> >>>> >>>> ___ >>>> OpenStack-operators mailing list >>>> OpenStack-operators@lists.openstack.org >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >>> >>> >>> ___ >>> OpenStack-operators mailing list >>> OpenStack-operators@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> >> >> ___ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators I'll moderate the packaging WG if needed. -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] release of openstack-kilo 2015.1.1 (gentoo)
Just got done finishing up the release (for those of you not using the live ebuilds, which I highly recommend). I've also added pre-install testing to nova. Let me know if you have issues. -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] New Gentoo Openstack images.
All of the issues that people reported should be fixed. If you have other issues, let me know. It looks like we will be making this (qemu) a catalyst target, so we should hopefully have these be official soon (and then it's in disk-image-builder fairly easily, either via stage4 (which I use for these) or the image itself. The list of closed bugs: https://github.com/prometheanfire/gentoo-cloud-prep/issues?q=is%3Aissue+is%3Aclosed http://gentoo.osuosl.org/experimental/amd64/openstack/ -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] OSAD for RHEL
On 07/07/2015 04:38 PM, Abel Lopez wrote: > Hey everyone, > I've started looking at osad, and I like much of the direction it takes. > I'm pretty interested in developing it to run on RHEL, I just wanted to check > if anyone would be -2 opposed to that before I spend cycles on it. > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > I have a change out there for adding support for alternate operating systems. (along with a blueprint). It's extreemly basic right now, but here are the links. It's on hold on my side (gentoo) for lack of manpower. https://blueprints.launchpad.net/openstack-ansible/+spec/os-ansible-for-gentoo-hosts https://review.openstack.org/#/c/199316/ -- -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Gentoo image availability
On 06/23/2015 12:17 AM, Matthew Thode wrote: > On 06/11/2015 10:12 AM, Matthew Thode wrote: >> On 06/11/2015 04:11 AM, Eren Türkay wrote: >>> On 10-06-2015 02:14, George Shuklin wrote: >>>> Aw. Don't discriminate DHCP. It has many nice features (for example, if >>>> you add >>>> new interface to existing VM, cloud-init with static config will ignore >>>> it, but >>>> DHCP will works like magic). >>>> >>>> I don't know how it works in Gentoo, but in Debian 'allow-hotplug' for all >>>> interfaces but eth0 allows to support most of the future interfaces. Same >>>> for >>>> CentOS - you can add few eth scripts to network configuration and they will >>>> works as soon as new interface appears. >>> >>> I want to add to this comment. I believe this hot-plug feature for ethernet >>> devices is essential in the cloud environment. Short time ago I needed to >>> move >>> port from one instance to another while keeping the internal IP address >>> same. I >>> achieved it by removing a port from the old instance, re-creating the port >>> with >>> the same ip address, and pluging it to the new instance. >>> >>> The downtime was minimal as the instance supported hot-plug (ubuntu 14.04) >>> and >>> the ip addresses were distributed using DHCP. When the interface was >>> re-plugged, dhclient requested an ip address and the DHCP server gave the >>> internal address of the port which I specified. >>> >>> So, it would be really great if you can support hot-plugging for ethernet >>> devices and DHCP. I find them very useful and I believe many people would >>> expect this feature from Gentoo image. >>> >>> Regards, >>> >>> >>> >>> ___ >>> OpenStack-operators mailing list >>> OpenStack-operators@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >> ya, it's probably the number one thing I want to see as well and the >> next thing I'm working on. >> >> >> >> ___ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > ok, updated the images. Did the following. > > 1. Allowed for any interface to get auto addressed (dhcpcd handles that > actually, no net configs needed). > > 2. The rootfs resizes on first boot now. > > 3. image size is reduced. > > 4. more profiles are now available. > > Notes... DIB is on my todo, but should be very minor, since I'm > generating more or less official openstack stage4 guest tarballs > already. Also, getting these images themselves official (within gentoo) > is next and kinda hard if only because it needs to be totally within > catalyst. > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > forgot the link, here it is. http://distfiles.gentoo.org/experimental/amd64/openstack/ -- -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Gentoo image availability
On 06/11/2015 10:12 AM, Matthew Thode wrote: > On 06/11/2015 04:11 AM, Eren Türkay wrote: >> On 10-06-2015 02:14, George Shuklin wrote: >>> Aw. Don't discriminate DHCP. It has many nice features (for example, if you >>> add >>> new interface to existing VM, cloud-init with static config will ignore it, >>> but >>> DHCP will works like magic). >>> >>> I don't know how it works in Gentoo, but in Debian 'allow-hotplug' for all >>> interfaces but eth0 allows to support most of the future interfaces. Same >>> for >>> CentOS - you can add few eth scripts to network configuration and they will >>> works as soon as new interface appears. >> >> I want to add to this comment. I believe this hot-plug feature for ethernet >> devices is essential in the cloud environment. Short time ago I needed to >> move >> port from one instance to another while keeping the internal IP address >> same. I >> achieved it by removing a port from the old instance, re-creating the port >> with >> the same ip address, and pluging it to the new instance. >> >> The downtime was minimal as the instance supported hot-plug (ubuntu 14.04) >> and >> the ip addresses were distributed using DHCP. When the interface was >> re-plugged, dhclient requested an ip address and the DHCP server gave the >> internal address of the port which I specified. >> >> So, it would be really great if you can support hot-plugging for ethernet >> devices and DHCP. I find them very useful and I believe many people would >> expect this feature from Gentoo image. >> >> Regards, >> >> >> >> ___ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > ya, it's probably the number one thing I want to see as well and the > next thing I'm working on. > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ok, updated the images. Did the following. 1. Allowed for any interface to get auto addressed (dhcpcd handles that actually, no net configs needed). 2. The rootfs resizes on first boot now. 3. image size is reduced. 4. more profiles are now available. Notes... DIB is on my todo, but should be very minor, since I'm generating more or less official openstack stage4 guest tarballs already. Also, getting these images themselves official (within gentoo) is next and kinda hard if only because it needs to be totally within catalyst. -- -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Gentoo image availability
On 06/11/2015 04:11 AM, Eren Türkay wrote: > On 10-06-2015 02:14, George Shuklin wrote: >> Aw. Don't discriminate DHCP. It has many nice features (for example, if you >> add >> new interface to existing VM, cloud-init with static config will ignore it, >> but >> DHCP will works like magic). >> >> I don't know how it works in Gentoo, but in Debian 'allow-hotplug' for all >> interfaces but eth0 allows to support most of the future interfaces. Same for >> CentOS - you can add few eth scripts to network configuration and they will >> works as soon as new interface appears. > > I want to add to this comment. I believe this hot-plug feature for ethernet > devices is essential in the cloud environment. Short time ago I needed to move > port from one instance to another while keeping the internal IP address same. > I > achieved it by removing a port from the old instance, re-creating the port > with > the same ip address, and pluging it to the new instance. > > The downtime was minimal as the instance supported hot-plug (ubuntu 14.04) and > the ip addresses were distributed using DHCP. When the interface was > re-plugged, dhclient requested an ip address and the DHCP server gave the > internal address of the port which I specified. > > So, it would be really great if you can support hot-plugging for ethernet > devices and DHCP. I find them very useful and I believe many people would > expect this feature from Gentoo image. > > Regards, > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ya, it's probably the number one thing I want to see as well and the next thing I'm working on. -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Gentoo image availability
On 06/09/2015 10:34 AM, Fox, Kevin M wrote: > Awesome. Are they ready enough that they should go into the app catalog? > (http://apps.openstack.org) > > Thanks, > Kevin > ________ > From: Matthew Thode [prometheanf...@gentoo.org] > Sent: Monday, June 08, 2015 8:26 AM > To: openstack-operators@lists.openstack.org > Subject: [Openstack-operators] Gentoo image availability > > Hi, > > I'm the packager of Openstack on Gentoo and have just started generation > of Gentoo Openstack images. Right now it is just a basic amd64 image, > but I plan on adding nomultilib and hardened variants (for a total of at > least 4 images). I plan on generating these images at least weekly > > These images are not yet sanctioned by our infra team, but I plan on > remedying that (being a member of said team should help). > > I am currently using the scripts at > https://github.com/prometheanfire/gentoo-cloud-prep to generate the > images (based on a heavily modified version of Matt Vandermeulen's > scripts). If you have any issues please submit bugs there or contact me > on irc (prometheanfire on freenode). > > Here's the link to the images, I'm currently gpg signing them with the > same key I use to sign this email (offline master key smartcard setup > for security minded folk). > > http://23.253.251.73/ > > Let me know if you have questions, > > -- > Matthew Thode (prometheanfire) > It could probably go into the catalog, but I'd rather get it generated and signed by our (gentoo's) infra first. -- -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Gentoo image availability
On 06/08/2015 09:17 PM, George Shuklin wrote: > Nice to hear. > > You're doing a great job! > > Few things to make Gentoo 'first class citizen' for openstack (guest). > > 1. Check if you supports for all eth's, not only eth0. If instance boots > with two or more interfaces, it should be able to get all it addresses. > > 2. Add Gentoo 'element' to disk-image-builder > (https://github.com/openstack/diskimage-builder) > > 3. Ship image with proper cloud-init cloud.cfg > > > On 06/08/2015 06:26 PM, Matthew Thode wrote: >> Hi, >> >> I'm the packager of Openstack on Gentoo and have just started generation >> of Gentoo Openstack images. Right now it is just a basic amd64 image, >> but I plan on adding nomultilib and hardened variants (for a total of at >> least 4 images). I plan on generating these images at least weekly >> >> These images are not yet sanctioned by our infra team, but I plan on >> remedying that (being a member of said team should help). >> >> I am currently using the scripts at >> https://github.com/prometheanfire/gentoo-cloud-prep to generate the >> images (based on a heavily modified version of Matt Vandermeulen's >> scripts). If you have any issues please submit bugs there or contact me >> on irc (prometheanfire on freenode). >> >> Here's the link to the images, I'm currently gpg signing them with the >> same key I use to sign this email (offline master key smartcard setup >> for security minded folk). >> >> http://23.253.251.73/ >> >> Let me know if you have questions, >> >> >> >> ___ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > Ya, not sure how to do multi-interface yet. I'd love if the cloud-init static ip support would work with it. (hash with macs being the key and a list of IPs being the value for each interface). Then dhcp can go away (I tend to much prefer config-drive). The disk-image-builder support is on my todo list already :D I just updated the cloud-init ebuild with a better cloud.cfg, could probably use more love, but it works. I am working on getting gentoo as a first class citizen in openstack-ansible as well, which depends on the disk-image-builder work. So much work still to do :D -- Matthew Thode (prometheanfire) ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Gentoo image availability
Hi, I'm the packager of Openstack on Gentoo and have just started generation of Gentoo Openstack images. Right now it is just a basic amd64 image, but I plan on adding nomultilib and hardened variants (for a total of at least 4 images). I plan on generating these images at least weekly These images are not yet sanctioned by our infra team, but I plan on remedying that (being a member of said team should help). I am currently using the scripts at https://github.com/prometheanfire/gentoo-cloud-prep to generate the images (based on a heavily modified version of Matt Vandermeulen's scripts). If you have any issues please submit bugs there or contact me on irc (prometheanfire on freenode). Here's the link to the images, I'm currently gpg signing them with the same key I use to sign this email (offline master key smartcard setup for security minded folk). http://23.253.251.73/ Let me know if you have questions, -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
