Re: [Openstack-operators] Draft Agenda for AUS Ops@Summit
Hey Tom, I can moderate the Mitaka: Beyond the Release Notes session if it is really needed and no one else has signed up to moderate. -- Melvin Hillsman Rackspace | OpenStack Innovation Center Ops Team Tech Lead Web: http://mrhillsman.com Email: mrhills...@gmail.com Office: (210) 312-1267 Mobile: (210) 413-1659 Voicemail: (210) 570-7056 Twitter: @mrhillsman LinkedIn: https://linkedin.com/in/mrhillsman IRC: mrhillsman ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] VPNaaS and FWaaS
Please take a moment to reach out to the Neutron team and visit the following. Could this resource be of use to address their concern? https://osic.org/clusters > On Apr 29, 2016, at 8:01 AM, Matt Jarvis > wrote: > > As some of you on this list may already know, there are issues in the Neutron > team with development resources on VPNaas and FWaaS, and there have been > discussions in Austin about deprecating the code from the main Neutron > codebase. The decision is currently that the code will remain for another 6 > months, after which time if no dev resource has emerged, then they will be > deprecated. > > I know there are operators relying on these functions, particularly in the > public cloud space in Europe, so this would impact those people. I also know > this list doesn't necessarily reach all of them either, so I will try and > reach out by other means as well, but it would be very useful to try and get > a clearer picture of how many people are using VPNaaS and FWaaS. If you are, > could you please respond to this thread ? > > If we have metrics that a constituent part of the user community need these > functions, then we can try and find a way to help the Neutron team to cover > the resourcing gaps. > > Matt > > DataCentred Limited registered in England and Wales no. 05611763 > ___ > 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
Re: [Openstack-operators] VPNaaS and FWaaS
Thanks for the feedback Lubosz. Is OSIC as well to be a resource for in demand (enterprise) features that the community does not have available resources (developers) to work on? Are there existing alternatives to these two (Octavia) which will pick up where these are being left and therefore there is not a high demand? > On Apr 29, 2016, at 8:43 AM, Kosnik, Lubosz wrote: > > The idea of OSIC clusters is to give people access to multi node environments > to test software in scale. There are a lot of thing which brakes in big scale. > If I'm right the problem is that there is not so many developers which are > working on this *asS but please tell if I'm wrong. > > Lubosz "diltram" Kosnik > OSIC team member > > Sent from my iPhone > > On 29 Apr 2016, at 8:19 AM, Melvin Hillsman wrote: > >> Please take a moment to reach out to the Neutron team and visit the >> following. Could this resource be of use to address their concern? >> https://osic.org/clusters >> >> On Apr 29, 2016, at 8:01 AM, Matt Jarvis >> wrote: >> >>> As some of you on this list may already know, there are issues in the >>> Neutron team with development resources on VPNaas and FWaaS, and there have >>> been discussions in Austin about deprecating the code from the main Neutron >>> codebase. The decision is currently that the code will remain for another 6 >>> months, after which time if no dev resource has emerged, then they will be >>> deprecated. >>> >>> I know there are operators relying on these functions, particularly in the >>> public cloud space in Europe, so this would impact those people. I also >>> know this list doesn't necessarily reach all of them either, so I will try >>> and reach out by other means as well, but it would be very useful to try >>> and get a clearer picture of how many people are using VPNaaS and FWaaS. If >>> you are, could you please respond to this thread ? >>> >>> If we have metrics that a constituent part of the user community need these >>> functions, then we can try and find a way to help the Neutron team to cover >>> the resourcing gaps. >>> >>> Matt >>> >>> DataCentred Limited registered in England and Wales no. 05611763 >>> ___ >>> 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
Re: [Openstack-operators] VPNaaS and FWaaS
Thank you Matt for the update and call to action. > On Apr 29, 2016, at 9:16 AM, Matt Jarvis > wrote: > > Yes the problem is exactly that there is a lack of developer resource on > VPNaaS and FWaaS specifically, and probably because these aren't functions > many vendors need. We'd like to explore what mechanisms there could be for > funding resource, but the most important thing right now is for all those > operators who need these functions to make themselves known so there is a > metric. > >> On 29 April 2016 at 08:43, Kosnik, Lubosz wrote: >> The idea of OSIC clusters is to give people access to multi node >> environments to test software in scale. There are a lot of thing which >> brakes in big scale. >> If I'm right the problem is that there is not so many developers which are >> working on this *asS but please tell if I'm wrong. >> >> Lubosz "diltram" Kosnik >> OSIC team member >> >> Sent from my iPhone >> >> On 29 Apr 2016, at 8:19 AM, Melvin Hillsman >> mailto:mrhills...@gmail.com>> wrote: >> >> Please take a moment to reach out to the Neutron team and visit the >> following. Could this resource be of use to address their concern? >> https://osic.org/clusters >> >> On Apr 29, 2016, at 8:01 AM, Matt Jarvis >> mailto:matt.jar...@datacentred.co.uk>> wrote: >> >> As some of you on this list may already know, there are issues in the >> Neutron team with development resources on VPNaas and FWaaS, and there have >> been discussions in Austin about deprecating the code from the main Neutron >> codebase. The decision is currently that the code will remain for another 6 >> months, after which time if no dev resource has emerged, then they will be >> deprecated. >> >> I know there are operators relying on these functions, particularly in the >> public cloud space in Europe, so this would impact those people. I also know >> this list doesn't necessarily reach all of them either, so I will try and >> reach out by other means as well, but it would be very useful to try and get >> a clearer picture of how many people are using VPNaaS and FWaaS. If you are, >> could you please respond to this thread ? >> >> If we have metrics that a constituent part of the user community need these >> functions, then we can try and find a way to help the Neutron team to cover >> the resourcing gaps. >> >> Matt >> >> DataCentred Limited registered in England and Wales no. 05611763 >> ___ >> 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<mailto:OpenStack-operators@lists.openstack.org> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > DataCentred Limited registered in England and Wales no. 05611763 ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [Large Deployments Team] Meeting Reminder - 20-May-2016 03:00 UTC
Thanks for the reminder Matt! -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org From: Matt Van Winkle Date: Thursday, May 19, 2016 at 10:17 AM To: "openstack-operators@lists.openstack.org" Subject: [Openstack-operators] [Large Deployments Team] Meeting Reminder - 20-May-2016 03:00 UTC Hello LDT folks! Just a reminder that our May meeting is in a little less than 12 hours. This month is or APAC friendly time slot. See you all in #openstack-operators tonight/tomorrow morning! Thanks! VW ___ 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
Re: [Openstack-operators] Ops Meetups Team - Inagural meeting - Tuesday 1400 UTC
+1 > On May 19, 2016, at 5:52 PM, Shamail wrote: > > > >> On May 19, 2016, at 6:23 PM, Edgar Magana wrote: >> >> This location sounds fantastic! I will go for Seattle! > +1 >> >> Edgar >> >>> On 5/17/16, 8:13 AM, "Kingshott, Daniel" >>> wrote: >>> >>> Just so we have this out there for the Seattle BestBuy location: >>> >>> 200 person theatre - Full A/V, VC facilities. >>> 6 breakout meeting rooms, one seats 5, the others seat 10+ - all have big >>> screens, whiteboards, A/V and V/C. We also have an office space area that >>> can be used (it¹s outside the security perimeter) that can seat 30. >>> Right on south lake union next to Amazon. >>> >>> Pretty flexible on dates, this is a huge office with few people in it >>> right now. >>> >>> Thanks, >>> >>> Dan >>> >>> >>> Daniel Kingshott >>> Cloud Dude >>> (425) 623 4359 - Cell >>> >>> Best Buy Co. Inc. >>> Technology Development Center >>> 1000 Denny Way | 8th Floor | Seattle, WA | 98109 | USA >>> >>> >>> >>> >>> On 5/17/16, 6:04 AM, "Tom Fifield" wrote: Reminder - this meeting is in an hour :) > On 14/05/16 11:44, Tom Fifield wrote: > Thank you all for the excellent response to our doodle poll. > > The inagural meeting of the Ops Meetups Team will be at: > > > Tuesday, 17 of May at 1400 UTC [1] > > > Let's meet in IRC[2], in the #openstack-operators channel. > > > > Details about the group, and the link to the agenda etherpad, can be > found at: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.openstack.org_wiki_Ops-5FMeetups-5FTeam-23Meeting-5FInformation&d=CwIFAw&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Di8Wn6mWDlnpQK56fi2sMmsBj_3Hx6RKjqlFgUAc6kc&s=B8PX5OIE2mxCYcBFf1T5tpauXbZ43zF0tDgGYR6SBQg&e= > > > > > Regards, > > > Tom > > > [1] To see this in your local time - check: > > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.timeanddate.com_worldclock_fixedtime.html-3Fmsg-3DOps-2BMeetups-2BTeam&d=CwIFAw&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Di8Wn6mWDlnpQK56fi2sMmsBj_3Hx6RKjqlFgUAc6kc&s=-xynLIaqA19_WVnXEIHXCBxSDAzFcUwNDil7B7WvUvY&e= > > &iso=20160517T22&p1=241 > > > [2] If you're new to IRC, there's a great guide here: > https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.openstack.org_upstream-2Dtraining_irc.html&d=CwIFAw&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Di8Wn6mWDlnpQK56fi2sMmsBj_3Hx6RKjqlFgUAc6kc&s=NVEstV9dQg0tavNWY99ciu8VR21IXJ2Ph9_N8MFNops&e= > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=CwIFAw&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Di8Wn6mWDlnpQK56fi2sMmsBj_3Hx6RKjqlFgUAc6kc&s=QRAtocVQcHV5Y72bAhNMdj4J0wVdihE9wssmGv7X5Ec&e= ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=CwIFAw&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Di8Wn6mWDlnpQK56fi2sMmsBj_3Hx6RKjqlFgUAc6kc&s=QRAtocVQcHV5Y72bAhNMdj4J0wVdihE9wssmGv7X5Ec&e= >>> >>> >>> ___ >>> OpenStack-operators mailing list >>> OpenStack-operators@lists.openstack.org >>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=CwIFAw&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=Di8Wn6mWDlnpQK56fi2sMmsBj_3Hx6RKjqlFgUAc6kc&s=QRAtocVQcHV5Y72bAhNMdj4J0wVdihE9wssmGv7X5Ec&e= >> >> ___ >> 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
Re: [Openstack-operators] Ops Meetups Team - Meeting Tuesday 1400 UTC
See you then :) > On May 30, 2016, at 10:40 PM, Tom Fifield wrote: > > Hi all, > > We're up for a meeting: > > Tuesday, 31 of May at 1400 UTC [1] > > > It's going to be an interesting one - it's a US holiday on the 30th, so > people might not remember that they have this very important meeting first > thing back! We'll see if it's necessary to postpone based on how many show up > :) > > > Anyway, let's meet in IRC[2], in the #openstack-operators channel. > > > Details about the group, and the link to the agenda etherpad, can be found at: > > https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information > > > > Regards, > > > Tom > > > [1] To see this in your local time - check: > http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team&iso=20160531T22&p1=241 > > [2] If you're new to IRC, there's a great guide here: > http://docs.openstack.org/upstream-training/irc.html > > > ___ > 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
Re: [Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News
Apologies, * On a side note, can we decide on a [email-subject-tag] to help filter these in [Openstack-operators] * Suggestion: [ops-meetups-team] For the delay that is since rain and Houston, TX fight a lot and rain is winning these days unfortunately. I was tasked with submitting to the ML a request to discuss how do we handle the waiting list for those who are not able to attend the Ops Midcycle due to the cap. Looking at EventBrite [ https://www.eventbrite.com/support/articles/en_US/How_To/how-to-set-up-an-event-waitlist?lg=en_US ] if we are going to do a waitlist, this looks like a great option where basically we get details about the attendees we need and the waitlist is automatically created once the cap is hit. Playing devil’s advocate, my only apprehension to this process is should the waitlist be large, and there is a significant reason for someone who attended a previous Ops Midcycle to need to attend the next, how would that be handled? I am sure there are other potential issues that can be identified. Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org On 6/1/16, 11:33 PM, "Tom Fifield" wrote: >Hello all, > >Thank you very much to the dozen of you who participated in our second >meeting. We had some fantastic discussion, summarised below (the meeting >overview can be found at [3] and the full log at [4]). > > >==Next Meeting== >Unless there is further discussion, this the next meeting is at: > >==> Tuesday, 14 of Jun at 1400 UTC[1] in #openstack-operators > >[2] will be kept up to date with information about the meeting time and >agenda > > >==August Meetup== >Since there really isn't a lot of time left and we have proposals >already, we decided for this time we would not do the open call. >So, gfa, shintano and I will be working behind the scenes with Bestbuy >(Seattle) and Bloomberg (NYC) a little bit to get further details on >their venues - we will report to the group as soon as we have some >progress so we can make a decision for the August meetup. > > > >==Meetup size== >We had a great discussion on meetup size and it's looking like 150-200 >is the proposal, please participate in Matt Jarvis' thread at: > >http://lists.openstack.org/pipermail/openstack-operators/2016-June/010607.html > > > > >==Waitlist management== >There was a good proposal on how to manage the waitlist (give those that >missed out first go at the next one). mrhillsman will write that up and >send it through to the list shortly. > > > > >Regards, > > >Tom > > >[1] >http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team&iso=20160614T22&p1=241 > >[2] https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information > >[3] >http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-31-14.01.html > >[4] >http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-31-14.01.log.html > >___ >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
Re: [Openstack-operators] Uptime and SLA's
Hey Matt, I am looking into Monasca and would like to know your recommendation for resources regarding a) understanding and b) installing the project; especially since there is no install guide on the project wiki. Additionally, can you shed some light on whether this setup would run behind a loadbalancer in an HA configuration; I am looking at using three servers which will house a “stack”/“toolchain” for such activities. Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org From: Matt Fischer Date: Thursday, June 2, 2016 at 5:29 PM To: "Kingshott, Daniel" Cc: OpenStack Operators Subject: Re: [Openstack-operators] Uptime and SLA's We do this a few different ways, some of which may meet your needs. For API calls we measure a simple, quick, and impactless call for each service (like heat stack-list) and we monitor East from West and vice versa. The goal here is nothing added to the DBs, so nothing like neutron net-create. The downside here is that some of these calls work even when the service isn't 100% healthy so keep that in mind. Then we also have a set of "what would a user do" calls like "spin up a VM and attach a FIP and ssh in" or "create and delete a volume". These run less often. Finally we have a reference cloud application that uses our LBaaS, GSLB, HA routers, and multiple front-end/back-end nodes. This has the highest expectation of uptime and is used as an example for our customers of how you can run an app with "more nines" than the underlying infra. On any of these, especially the first two I mentioned, time series data is super useful. It's good to know that your create volume times (for example) are 40% slower after your deploy. We use Monasca and Grafana for that. On Thu, Jun 2, 2016 at 2:37 PM, Kingshott, Daniel wrote: We¹re currently in the process of writing up an internal SLA for our openstack cloud, I¹d be interested to hear what others have done and what metrics folks are capturing. My initial thoughts are success / fail spawning instances, creating and attaching volumes, API availability and so on. Can anyone on the list share their insights? Thanks, Dan Daniel Kingshott Cloud Dude (425) 623 4359 - Cell Best Buy Co. Inc. Technology Development Center 1000 Denny Way | 8th Floor | Seattle, WA | 98109 | USA ___ 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
Re: [Openstack-operators] Uptime and SLA's
Really appreciate the feedback. > On Jun 2, 2016, at 6:51 PM, Bak, Ryan M wrote: > > Melvin, > > The Monasca wiki (https://wiki.openstack.org/wiki/Monasca) has a lot of > information on architecture, as well as links to several talks given at > summits over the past couple years. That’s probably your best bet for > general information and understanding. There isn’t any single install guide > that I’m aware of, but you can bring up a working Monasca stack in Devstack > (https://github.com/openstack/monasca-api/tree/master/devstack) and take a > look at that, and there is also a puppet module for Monasca setup available > here: https://github.com/openstack/puppet-monasca. Even if you’re not using > puppet that will give you a sense of what you’ll need and how to set > everything up. > > Monasca can definitely run in an HA configuration. In production we run > three load balanced nodes in each region with the api stack (monasca-api, > monasca-persister, monasca-thresh, kafka and storm). We also have a separate > cluster of nodes in each region running Vertica for our backend, and we use > Kafka to replicate the data across regions so that the data is global. If > you want a diagram of our setup, you can find one in our talk from the Austin > summit > (https://www.youtube.com/watch?v=uBapdsOpND4&feature=youtu.be&t=17m53s). > Feel free to reach out here or on the Monasca IRC channel if you run into any > difficulties setting up Monasca, or have any other questions. > > -Ryan Bak > > From: Melvin Hillsman > Date: Thursday, June 2, 2016 at 4:58 PM > To: Matt Fischer , "Kingshott, Daniel" > > Cc: OpenStack Operators > Subject: Re: [Openstack-operators] Uptime and SLA's > Resent-From: Ryan Bak > > Hey Matt, > > I am looking into Monasca and would like to know your recommendation for > resources regarding a) understanding and b) installing the project; > especially since there is no install guide on the project wiki. Additionally, > can you shed some light on whether this setup would run behind a loadbalancer > in an HA configuration; I am looking at using three servers which will house > a “stack”/“toolchain” for such activities. > > Kind regards, > -- > Melvin Hillsman > Ops Technical Lead > OpenStack Innovation Center > mrhills...@gmail.com > phone: (210) 312-1267 > mobile: (210) 413-1659 > Learner | Ideation | Belief | Responsibility | Command > http://osic.org > > From: Matt Fischer > Date: Thursday, June 2, 2016 at 5:29 PM > To: "Kingshott, Daniel" > Cc: OpenStack Operators > Subject: Re: [Openstack-operators] Uptime and SLA's > > We do this a few different ways, some of which may meet your needs. > > For API calls we measure a simple, quick, and impactless call for each > service (like heat stack-list) and we monitor East from West and vice versa. > The goal here is nothing added to the DBs, so nothing like neutron > net-create. The downside here is that some of these calls work even when the > service isn't 100% healthy so keep that in mind. > > Then we also have a set of "what would a user do" calls like "spin up a VM > and attach a FIP and ssh in" or "create and delete a volume". These run less > often. > > Finally we have a reference cloud application that uses our LBaaS, GSLB, HA > routers, and multiple front-end/back-end nodes. This has the highest > expectation of uptime and is used as an example for our customers of how you > can run an app with "more nines" than the underlying infra. > > On any of these, especially the first two I mentioned, time series data is > super useful. It's good to know that your create volume times (for example) > are 40% slower after your deploy. We use Monasca and Grafana for that. > > >> On Thu, Jun 2, 2016 at 2:37 PM, Kingshott, Daniel >> wrote: >> We¹re currently in the process of writing up an internal SLA for our >> openstack cloud, I¹d be interested to hear what others have done and what >> metrics folks are capturing. >> >> My initial thoughts are success / fail spawning instances, creating and >> attaching volumes, API availability and so on. >> >> Can anyone on the list share their insights? >> >> Thanks, >> >> Dan >> >> >> Daniel Kingshott >> Cloud Dude >> (425) 623 4359 - Cell >> >> Best Buy Co. Inc. >> Technology Development Center >> 1000 Denny Way | 8th Floor | Seattle, WA | 98109 | USA >> >> >> ___ >> 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
Re: [Openstack-operators] Upgrade OpenStack Juno to Mitaka
+1 on Saverio's response. You will want to upgrade to Mitaka by NOT jumping releases; J - K - L - M not J - M On Wed, Jun 15, 2016 at 4:13 AM, Saverio Proto wrote: > Hello, > > first of all I suggest you read this article: > > http://superuser.openstack.org/articles/openstack-upgrading-tutorial-11-pitfalls-and-solutions > > > What is the best way to performe an upgrade from Juno to Mitaka? > > I would go for the in place upgrade, but I always upgraded without > jumping version, that AFAIK is not supported. > > The main problem I see, is that database migrations are supported when > you upgrade to the next release, but if you jump form Juno to Mitaka I > have to idea how the database upgrade cloud be done. > > Saverio > > ___ > 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
Re: [Openstack-operators] [kolla] question of default users for operators
Personally, if OpenStack default is to have a member or _member_ as an operator I would prefer there be a user according to the default. Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org From: "Steven Dake (stdake)" Date: Friday, July 29, 2016 at 10:35 PM To: "openstack-operators@lists.openstack.org" Subject: [Openstack-operators] [kolla] question of default users for operators Hey folks, In Kolla we have a significant bug in that Horizon can't be used because it requires a member user. We have a few approaches to fixing this problem in mind, but want to understand what Operators want. Devstack itself has switched between member and _member_ although Devstack isn't our reference: Operators are. Which of those do operators prefer (if either). Another question was whether we should create a default user named "user" and use this in place of member. Thoughts welcome. Regards -steve ___ 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
Re: [Openstack-operators] Installing mitaka's image service error
As suggested in the referenced email, have you checked your logs? Additionally check to be sure that your MySQL connection information is correct and that MySQL is bound to the IP address that resolves to "controller" as you have in your connection string. Hopefully some of this helps you get to a resolution. Kind regards, Melvin Hillsman On Jul 31, 2016, at 6:46 PM, 张余歌 wrote: My error is the same as this link: http://lists.openstack.org/pipermail/openstack-operators/2016-March/009821.html But I can't solve this problem,have somebody know how to solve?thanks a lot 從我的 Windows Phone 寄出 ___ 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
Re: [Openstack-operators] [kolla] question of default users for operators
I think even more so would be what is the purpose/benefit to an operator? 99.99% of the time an operator will have an idea of resources they want to create already or plans to do so. Personally, unless pushing to demo OpenStack, I would prefer totally untouched install. > On Jul 31, 2016, at 8:13 PM, Blair Bethwaite > wrote: > > Sounds like a recipe for confusion? > >> On 1 August 2016 at 10:23, Steven Dake (stdake) wrote: >> >> >>> On 7/31/16, 7:13 AM, "Jay Pipes" wrote: >>> On 07/29/2016 11:35 PM, Steven Dake (stdake) wrote: Hey folks, In Kolla we have a significant bug in that Horizon can't be used because it requires a member user. We have a few approaches to fixing this problem in mind, but want to understand what Operators want. Devstack itself has switched between member and _member_ although Devstack isn't our reference: Operators are. Which of those do operators prefer (if either). Another question was whether we should create a default user named "user" and use this in place of member. >>> >>> "member" is a role, not a user. The default unprivileged user is named >>> "demo" and has the "member" role in a project called "demo". >> >> Yup, thanks for the correction. >> >>> >>> Are you asking what the name of the unprivileged *role* should be by >>> default in Kolla installations? Or are you asking what, if any, a >>> default unprivileged *user* should be called? >> >> The idea of adding a user called "user" with a role called "user" was >> proposed. Curious if operators care to want that. >> >> Regards >> -steve >> >>> >>> Best, >>> -jay >>> >>> ___ >>> 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 > > > > -- > Cheers, > ~Blairo > > ___ > 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] [openstack-operators] Ops Midcycle Evening Event!
Hey everyone, If you have not heard already, surely you will be hearing soon, the Ops Midcycle is coming August 25 and 26th! After the first day we are looking to have an evening event and this is a great opportunity for sponsorship. We are asking that if you think or know your company would be interested in sponsoring the evening event to reply back and we can get the details worked out. Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [openstack-operators] Ops Midcycle Evening Event!
Hey everyone, If you have not heard already, surely you will be hearing soon, the Ops Midcycle is coming August 25 and 26th! After the first day we are looking to have an evening event and this is a great opportunity for sponsorship. We are asking that if you think or know your company would be interested in sponsoring the evening event to reply back and we can get the details worked out. Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Ops Meetups Team - Next Meeting Coordinates and News
I beg to differ, it is not you, but the date that messed up! :P all is forgiven. Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org On 8/8/16, 5:46 PM, "Tom Fifield" wrote: >As usual, I have messed up the date. Email updated below with correct >information. > >On 廿十六年八月八日 暮 03:45, Tom Fifield wrote: >> Ops Meetups Team, >> >> Cheers for your great work in the last meeting. We had some fantastic >> discussion, and a special guest appearance from Allison Price. The >> meeting overview can be found at [3]). >> >> >> ==Next Meeting== >> Unless there is further discussion, this the next meeting is at: >> >> ==> Tuesday, 9 of Aug at 1400 UTC[1] in #openstack-operators >> >> [2] will be kept up to date with information about the meeting time and >> agenda >> >> >> ==August Meetup== >> NYC is tracking well. We have 83 registered so far, and have been >> working on the agenda - expect to discuss that at this meeting and get a >> draft on the ops ML ASAP. Then the process of finding moderators will >> start. >> >> We still need a sponsor for our evening event. Multiple companies >> chipping in together would be ideal. See the email from Melvin: >> >> http://lists.openstack.org/pipermail/openstack-operators/2016-August/011153.html >> >> >> >> >> ==Meetup promotion== >> We had a great discussion on meetup promotion and confirmed the list of >> tasks we plan to do to promote the meetups appropriately to ensure we >> get new people coming and also make sure they're cloud ops. See >> Allison's summary here: >> >> http://lists.openstack.org/pipermail/openstack-operators/2016-August/011152.html >> >> >> >> >> >> >> >> Regards, >> >> >> Tom >> >> >> [1] >> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team&iso=20160809T22&p1=241 >> >> >> [2] https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information >> >> [3] >> http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-08-02-14.00.html >> > >___ >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
Re: [Openstack-operators] Help
Are you ok? Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org On 8/9/16, 8:16 AM, "Patricia Dugan" wrote: > > >sent from the road > >> On Aug 9, 2016, at 5:00 AM, openstack-operators-requ...@lists.openstack.org >> wrote: >> >> Send OpenStack-operators mailing list submissions to >>openstack-operators@lists.openstack.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> or, via email, send a message with subject or body 'help' to >>openstack-operators-requ...@lists.openstack.org >> >> You can reach the person managing the list at >>openstack-operators-ow...@lists.openstack.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of OpenStack-operators digest..." >> >> >> Today's Topics: >> >> 1. Re: migration leaves instance in VERIFY_RESIZE and does not >> clean up source host resources (Gustavo Randich) >> 2. Re: [nova] can we lock RPC version withupgrade_levels on >> neutron-openvswitch-agent ? (Ihar Hrachyshka) >> 3. Re: [nova] can we lock RPC version with upgrade_levels on >> neutron-openvswitch-agent ? (Micha? Jastrz?bski) >> 4. Ops Meetups Team - Next Meeting Coordinatesand News (Tom Fifield) >> 5. Re: Ops Meetups Team - Next MeetingCoordinates and News >> (Tom Fifield) >> 6. Re: Ops Meetups Team - Next Meeting Coordinates and News >> (Melvin Hillsman) >> 7. Re: VirtIO and IDE disk (Emilio Moreno Fernandez) >> >> >> -- >> >> Message: 1 >> Date: Mon, 8 Aug 2016 18:31:21 -0300 >> From: Gustavo Randich >> To: "openstack-operators@lists.openstack.org" >> >> Subject: Re: [Openstack-operators] migration leaves instance in >>VERIFY_RESIZE and does not clean up source host resources >> Message-ID: >> >> Content-Type: text/plain; charset="utf-8" >> >> Sorry, I forgot to run 'nova resize-confirm' >> >> >> On Mon, Aug 8, 2016 at 6:17 PM, Gustavo Randich >> wrote: >> >>> Hi folks, >>> >>> I'm using Mitaka, and when running "nova migrate ", once >>> the instance is migrated OK to other host, it remains forever in >>> VERIFY_RESIZE status (not ACTIVE). There are no errors in the log. >>> >>> Also, in the source host, the directory >>> /var/lib/nova/instances/_resize >>> is left with disk, disk.info files, etc. in it, and the virsh domain >>> remains defined (but in shut off state). >>> >>> Is all this expected? >>> >>> Thanks! >>> >>> Gustavo >> -- next part -- >> An HTML attachment was scrubbed... >> URL: >> <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160808/c75e2be3/attachment-0001.html> >> >> -- >> >> Message: 2 >> Date: Tue, 9 Aug 2016 00:02:14 +0200 >> From: Ihar Hrachyshka >> To: Micha? Jastrz?bski >> Cc: OpenStack Operators >> Subject: Re: [Openstack-operators] [nova] can we lock RPC version with >>upgrade_levels on neutron-openvswitch-agent ? >> Message-ID: <65705cac-d022-4c3a-b0e5-76e4ba4b2...@redhat.com> >> Content-Type: text/plain; charset=utf-8; delsp=yes; format=flowed >> >> (Adding back ops@) >> >> Micha? Jastrz?bski wrote: >> >>> Yes, but it's a bit different. Difference being if you're doing it >>> right, you can keep nova running during upgrade. Can't say the same >>> for neutron. >> >> There is ongoing work to make it possible. The way it looks now, it will >> take Ocata the least. Till that happy time, you should indeed all >> controllers before upgrading database. >> >> That said, you can still run your agents while you upgrade your controller >> nodes. Once you are done with controllers, you can upgrade one remaining >> node running agents at a time. >> >> Ihar >> >> >> >> -- >> >> Message: 3 >> Date: Mon, 8 Aug 2016 17:06:34 -0500 >> From: Mic
Re: [Openstack-operators] Mid-Cycle Meetup, NYC, August 25th, call for additional working group sessions
Should not have been deleted as that would not be acceptable practice. Do you happen to still have what you commented? > On Aug 9, 2016, at 11:45 AM, Kruithof Jr, Pieter > wrote: > > Hiya, > > I added a note to the documentation session, but noticed it had disappeared a > few hours later. I just was curious to know whether it was deleted or > somehow wasn’t saved to the etherpad. > > Is deleting other folks comments fair game? I would hope they would be > crossed-out with a comment why. > > Thanks, > > Piet > > > > From: Chris Morgan > Date: Monday, August 8, 2016 at 3:18 PM > To: OpenStack Operators > Subject: [Openstack-operators] Mid-Cycle Meetup, NYC, August 25th, call for > additional working group sessions > > Hello Everyone, > The itinerary for the meet up is starting to come together nicely. We have > landed the general sessions on the main stage fairly well I feel. However, we > can fit more working group proposals into the venue but need some more topics. > > The etherpad for suggestions is here : > > https://etherpad.openstack.org/p/NYC-ops-meetup > > and the current state of the itinerary is here > > https://docs.google.com/spreadsheets/d/1EUSYMs3GfglnD8yfFaAXWhLe0F5y9hCUKqCYe0Vp1oA/edit?pref=2&pli=1#gid=1046944156 > > Please contribute by adding topics and/or +1ing existing topics. This > itinerary will be discussed in the IRC meeting tomorrow, which I believe Tom > will be sending out his handy reminder for soon. > > Chris > > -- > Chris Morgan > ___ > 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
Re: [Openstack-operators] cURL call at the end of provisioning and deprovisioning
+1 on nova notifications. Was reading over it and looks to be exactly what you want with a little bit of work. -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org On 8/15/16, 9:35 AM, "Ben Morrice" wrote: >You probably want to investigate the nova notification message queue and >writing something custom that listens to that. > >Specifically the messages 'compute.instance.create.end' and >'compute.instance.delete.end'. > >Here is a basic example to get you started: >http://alesnosek.com/blog/2015/05/25/openstack-nova-notifications-subscriber/ > >Kind regards, > >Ben Morrice > >__ >Ben Morrice | e: ben.morr...@epfl.ch | t: +41-21-693-9670 >EPFL ENT CBS BBP >Biotech Campus >Chemin des Mines 9 >1202 Geneva >Switzerland > >On 15/08/16 16:08, William Josefsson wrote: >> Yes thanks Tomas. I thought of the nova boot --user-data myscript.sh >> option, but I'm not sure how that would manage a deprovisioning. nova >> delete myvm, at this point I also wanna run a delete script than to >> delete the A-record, or is that possible? thx! Will >> >> On Mon, Aug 15, 2016 at 7:59 PM, Tomáš Vondra wrote: >>> Hi Will! >>> You may want one of two things: >>> a) OpenStack Designate, which is a DNS as a Service system integrated with >>> Nova. It will add a record for every instance in a zone you delegate to it. >>> b) Cloud-init. It runs in nearly every OpenStack Linux OS image and is >>> configured by /etc/cloud/cloud.cfg. There you will see a module that does a >>> curl call at the end of the boot process. You don't have to modify the >>> image, it takes configuration as a user-data script. >>> Tomas >>> >>> >>> Původní zpráva >>> Odesílatel: William Josefsson >>> Odesláno: 14. srpna 2016 17:54:45 SELČ >>> Komu: openstack-operators@lists.openstack.org >>> Předmět: [Openstack-operators] cURL call at the end of provisioning and >>> deprovisioning >>> >>> Hi list, >>> >>> I wanted to make a cURL call once an instance provisioning finished, >>> and also when an instance gets deprovisioned. I will make a http call >>> to PowerDNS for registration and deregistration of A record. >>> >>> Is there any way to run a common for a instance once it is finished >>> provisioning and when it gets deprovisioned? >>> >>> thx, will >>> >>> ___ >>> 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
Re: [Openstack-operators] thanks for the great time in NYC ! great Ops Meetup !
It was a pleasure to meet everyone and I hope I can continue to be a resource to the community. I have spoken to individuals I work with and they are just as excited as I am to assist with helping OpenStack operations community. I would like to also thank Chris and Bloomberg for hosting a great even and Tom Fifield for entrusting the community with the task of organizing the mid-cycle. I hope to continue to build great and lasting relationships with many of you in the near future. See you in Barcelona! Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center | Rackspace mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org From: Edgar Magana Date: Monday, August 29, 2016 at 3:36 PM To: Chris Morgan, Saverio Proto Cc: OpenStack Operators Subject: Re: [Openstack-operators] thanks for the great time in NYC ! great Ops Meetup ! Yes! Kudos to the team for organizing such a great event. It is a very grateful experience to learn from other and sharing all our good and bad experinces. Let’s rule Ops Session in Barcelona for sure! Edgar From: Chris Morgan Date: Monday, August 29, 2016 at 1:26 PM To: Saverio Proto Cc: OpenStack Operators Subject: Re: [Openstack-operators] thanks for the great time in NYC ! great Ops Meetup ! Thanks for the kind words. I am so glad it worked out. I want to repeat that Tom still did a lot of the work despite us attempting to pull the organizing of these events more into the general community. I hope to make it to Barcelona and see you there! Cheers, Chris On Mon, Aug 29, 2016 at 3:21 PM, Saverio Proto wrote: Hello ! I would like to thank Chris for all the work done to host our Ops Meetup. I had a great time in NYC, and I came back to Switzerland with a lot of input for work to do. Also thanks to all of you that participated. It was great to share experiences on Openstack operations with so many people. I really encourage anyone on this list to participate to these Openstack events, because the value is really extraordinary. I hope to see most of you guys in Barcelona for the summit. Cheers, Saverio ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Chris Morgan ___ 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
Re: [Openstack-operators] Ops Meetups Team - Meeting Reminder
#openstack-operators -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com <mailto:centermrhills...@gmail.com> phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org On 10/4/16, 9:39 AM, "Edgar Magana" wrote: >Hello All, > >I am trying to join the meeting but I am not sure which IRC channel you use. > >Edgar > >On 10/4/16, 5:30 AM, "Matt Van Winkle" wrote: > >Hey Ops Meetup folks, > >Gentle reminder that the meeting is in about 1.5 hours at 14:00 UTC. I > won’t be able to make it because of an all-day planning meeting. Hopefully, > Tom will be around to help manage the chaos. Edgar should be joining to talk > about the UC sessions and how we can help with those. Also, we need to > further refine the schedule. I’ve made some notes in the ehterpad [1] > > > >Thanks! > >VW > > > >[1] > https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_ops-2Dmeetups-2Dteam&d=DQIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=5OOWM-nMlcl9Vc6QqIS3VJhGcj2VdyYOmTqhyMNIK8c&s=SYB5RddFgQ2KUjQ0-ZY3Ajq2uhuWMN6-Nq-ZK3N48Jg&e= > > > > >___ >OpenStack-operators mailing list >OpenStack-operators@lists.openstack.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Doperators&d=DQIGaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=5OOWM-nMlcl9Vc6QqIS3VJhGcj2VdyYOmTqhyMNIK8c&s=hu8MgvT0ZRfyCbRxSG-uzV10I5fLvMTfrP7YP8Cy6aA&e= > > > >___ >OpenStack-operators mailing list >OpenStack-operators@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Ops@Barcelona - Updates
I was going to grab a few more sessions but have a talk on Tuesday @3:55. If someone wants to take Horizon which is during the same time of the talk, I can cover an earlier session. On 10/17/2016 01:22 AM, Tom Fifield wrote: On 17/10/16 14:17, John Dickinson wrote: I'm happy to moderate the Swift session, but I cannot make it at 3:05. If it's switched with a session in the earlier slot (2:15), then I'll be happy to lead that one. If not, I may be able to find another moderator, but I won't be able to be there. Done & Done! Thanks John :) https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/17353/ops-swift-feedback --John On 16 Oct 2016, at 21:58, Tom Fifield wrote: Hi all, There have been some schedule updates for the Ops design summit sessions: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ops+Summit%3A New Sessions added: * Ops Meetups Team * Some working groups not previously listed * Horizon: Operator and Plugin Author Feedback * Neutron: End user and operator feedback * Barbican: User and Operator Feedback Session and some minor room and time changes too - please doublecheck your schedule! ** Call for Moderators ** We really need a moderator for: >> * HAProy, MySQL, Rabbit Tuning since it looks like it will be one of the most popular sessions, but we don't have a moderator yet. These sessions will be canceled unless we can find a moderator: >> * Fleet Management >> * Swift >> * Horizon >> * Alt Deployment tech >> * ControlPlane Design(multi region) For those of you who want to know what it takes check out the Moderator's Guide: https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide & ask questions - we're here to help! 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 -- Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com mobile: (210) 413-1659 office: (210) 312-1267 Learner | Ideation | Belief | Responsibility | Command http://osic.org ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Ops@Barcelona - Updates
Hey everyone, I as well will be in Barcelona moderating a couple of sessions and would appreciate any comments/concerns/questions/discussions be added to relevant etherpads and/or emailed to me directly. On 10/17/2016 12:41 PM, Chris Morgan wrote: Hello Operators, It's just about one week until Barcelona, so here's a reminder: The operators sessions at Barcelona all have a dedicated etherpads for you to submit talking points. The master list of those for Barcelona is + I am moderating a couple and would like to encourage more content be added to those ether pads, namely Hardware (https://etherpad.openstack.org/p/BCN-ops-hardware) and particularly Ceph https://etherpad.openstack.org/p/BCN-ops-ceph which is in need of more content. I'd be willing to update these ether pads if anyone cares to email me ideas on what we should discuss in response to this email. For those of you going, see you in Spain! Chris On Mon, Oct 17, 2016 at 12:58 AM, Tom Fifield <mailto:t...@openstack.org>> wrote: Hi all, There have been some schedule updates for the Ops design summit sessions: https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ops+Summit%3A <https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Ops+Summit%3A> New Sessions added: * Ops Meetups Team * Some working groups not previously listed * Horizon: Operator and Plugin Author Feedback * Neutron: End user and operator feedback * Barbican: User and Operator Feedback Session and some minor room and time changes too - please doublecheck your schedule! ** Call for Moderators ** We really need a moderator for: >> * HAProy, MySQL, Rabbit Tuning since it looks like it will be one of the most popular sessions, but we don't have a moderator yet. These sessions will be canceled unless we can find a moderator: >> * Fleet Management >> * Swift >> * Horizon >> * Alt Deployment tech >> * ControlPlane Design(multi region) For those of you who want to know what it takes check out the Moderator's Guide: https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide <https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide> & ask questions - we're here to help! Regards, Tom ___ 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 <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators> -- Chris Morgan mailto:mihali...@gmail.com>> ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com mobile: (210) 413-1659 office: (210) 312-1267 Learner | Ideation | Belief | Responsibility | Command http://osic.org ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] openstack-ansible - recovery of failed infrastructure host
Hey Ben, Unfortunately I do not have way to confirm with you right now but also suggest you create a backup of your database as a matter of caution and general best practice. If you can backup anything else that would be a good thing to consider as well. Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org On 10/24/16, 12:06 PM, "Jesse Pretorius" wrote: Hi Ben, If you stand up a new infrastructure host with the same IP address and name in openstack_user_config then execute the setup-hosts, setup-infrastructure and setup-openstack plays it should put everything back in place for you without further intervention. Jesse IRC: odyssey4me On 10/24/16, 9:58 AM, "Ben Lagunilla" wrote: Hi All, How do we go about restoring a failed infrastructure host? Setup is openstack mitaka with high availability configured on 3 infrastructure hosts. Thanks! ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com and delete the original message. Your cooperation is appreciated. ___ 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
Re: [Openstack-operators] Updating oschecks
Hey Lars, I think the needs you have are relevant to anyone who would use this tooling and think you should definitely move forward with implementing what you have prototyped. I personally believe any improvements to the tools in osops repos are welcome. Bringing modularity to this as well is great from my perspective. On 11/03/2016 01:03 PM, Lars Kellogg-Stedman wrote: I've recently started working with the oscheck scripts in the osops-tools-monitoring project [1], and I found that in their current form they didn't quite meet my needs. In particular: - They don't share a common set of authentication options - They can't read credentials from files - Many of them require a priori configuration of the openstack environment, which means they can't be used to health check a new deployment I've spent a little time recently prototyping a new set of health check scripts, available here: https://github.com/larsks/oschecks I'd like to emphasize that these *are not* currently meant as a usable replacement for the existing checks; they were to prototype (a) the way I'd like the user interface to work and (b) the way I'd like things like credentials to work. This project offers the following features: - They use os_client_config for managing credentials, so they can be configured from a clouds.yaml file, or the environment, or the command line, and it all Just Works. - Authentication is handled in just one place in the code for all the checks. - The checks are extensible (using the cliff framework), which means that checks with different sets of requirements can be packaged/installed separately. See, for example: https://github.com/larsks/oschecks_systemd - For every supported service there is a simple "can I make an authenticated request to the API successfully" check that does not require any pre-existing resources to be created. - They are (hopefully) structured such that it is relatively easy to write new checks the follow the same syntax and behavior of the other checks. If people think this is a useful way of implementing these health checks, I would be happy to do the work necessary to make them a mostly drop-in replacement for the existing checks (adding checks that are currently missing, and adding appropriate console-script entrypoints to match the existing names, etc). I would appreciate any feedback. Sorry for the long message, and thanks for taking the time to read this far! [1]: https://github.com/openstack/osops-tools-monitoring/tree/master/monitoring-for-openstack/oschecks ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com mobile: (210) 413-1659 office: (210) 312-1267 Learner | Ideation | Belief | Responsibility | Command http://osic.org ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Help - Trying to install OpenStack - Network issues
Hey Rafael, Do you have bonding and 8021q kernel modules loading as well as bridge-utils and if-enslave packages. -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org > On Nov 7, 2016, at 12:17, Rafael Azevedo wrote: > > Hello guys, > > Im new to OpenStack and am following instructions from Ansible [1] in > order to get it installed. > > I've added the following config into my network init script: > > === > > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > auto em1 > iface em1 inet manual > bond-master bond0 > > auto em2 > iface em2 inet manual > bond-master bond0 > > auto em3 > iface em3 inet manual > bond-master bond0 > > auto em4 > iface em4 inet manual > bond-master bond0 > > > auto bond0 > iface bond0 inet static >address A.B.C.D >netmask 255.255.255.240 >network X.X.X.X > # broadcast 200.49.47.175 >gateway X.X.X.X ># dns-* options are implemented by the resolvconf package, if installed >dns-nameservers 8.8.8.8 >dns-search iagente.net.br >bond-mode 4 >bond-miimon 100 >bond-lacp-rate 1 >bond-slaves all > > > auto bond0.5 > iface bond0.5 inet static >address 10.196.188.2 >netmask 255.255.252.0 >vlan-raw-device bond0 > > # Container/Host management VLAN interface > auto bond0.10 > iface bond0.10 inet manual >vlan-raw-device bond0 > > # OpenStack Networking VXLAN (tunnel/overlay) VLAN interface > auto bond0.30 > iface bond0.30 inet manual >vlan-raw-device bond0 > > # Storage network VLAN interface (optional) > auto bond0.20 > iface bond0.20 inet manual >vlan-raw-device bond0 > > # Container/Host management bridge > auto br-mgmt > iface br-mgmt inet static >bridge_stp off >bridge_waitport 0 >bridge_fd 0 >bridge_ports bond0.10 >address 172.29.236.11 >netmask 255.255.252.0 >gateway 172.29.236.1 >dns-nameservers 8.8.8.8 8.8.4.4 > > # OpenStack Networking VXLAN (tunnel/overlay) bridge > # > # Only the COMPUTE and NETWORK nodes must have an IP address > # on this bridge. When used by infrastructure nodes, the > # IP addresses are assigned to containers which use this > # bridge. > # > auto br-vxlan > iface br-vxlan inet manual >bridge_stp off >bridge_waitport 0 >bridge_fd 0 >bridge_ports bond0.30 > > # compute1 VXLAN (tunnel/overlay) bridge config > #auto br-vxlan > #iface br-vxlan inet static > #bridge_stp off > #bridge_waitport 0 > #bridge_fd 0 > #bridge_ports bond0.30 > #address 172.29.240.12 > #netmask 255.255.252.0 > > # OpenStack Networking VLAN bridge > auto br-vlan > iface br-vlan inet manual >bridge_stp off >bridge_waitport 0 >bridge_fd 0 >bridge_ports bond0 > > # Storage bridge (optional) > # > # Only the COMPUTE and STORAGE nodes must have an IP address > # on this bridge. When used by infrastructure nodes, the > # IP addresses are assigned to containers which use this > # bridge. > # > auto br-storage > iface br-storage inet manual >bridge_stp off >bridge_waitport 0 >bridge_fd 0 >bridge_ports bond0.20 > > # compute1 Storage bridge > #auto br-storage > #iface br-storage inet static > #bridge_stp off > #bridge_waitport 0 > #bridge_fd 0 > #bridge_ports bond0.20 > #address 172.29.244.12 > #netmask 255.255.252.0 > > === > > But after I reboot the server, I lost connectivity and the server's > network wont work. > > Can anybody please help me out? > > What am I doing wrong? > > Thanks in advance. > > BR, > > R > > -- > [1]: > http://docs.openstack.org/developer/openstack-ansible/install-guide/app-config-test.html#test-environment-config > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Ops Meetups Team - Meeting Reminder
UTC does not care about DST good people. Just a reminder for those of us who do observe DST that the meeting is one hour earlier than previously: http://www.worldtimebuddy.com/?pl=1&lid=5128581,100,4699066,5746545&h=5128581 Meeting is always 1400 UTC should clear up any future concerns :) -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org Begin forwarded message: > From: Matt Van Winkle > Date: October 4, 2016 at 07:30:16 CDT > To: OpenStack Operators > Subject: [Openstack-operators] Ops Meetups Team - Meeting Reminder > > Hey Ops Meetup folks, > Gentle reminder that the meeting is in about 1.5 hours at 14:00 UTC. I won’t > be able to make it because of an all-day planning meeting. Hopefully, Tom > will be around to help manage the chaos. Edgar should be joining to talk > about the UC sessions and how we can help with those. Also, we need to > further refine the schedule. I’ve made some notes in the ehterpad [1] > > Thanks! > VW > > [1] https://etherpad.openstack.org/p/ops-meetups-team > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [openstack-operators] Ops Meetup Team Meeting Reminder
UTC does not care about DST good people. Just a reminder for those of us who do observe DST that the meeting is one hour earlier than previously: http://www.worldtimebuddy.com/?pl=1&lid=5128581,100,4699066,5746545&h=5128581 Meeting is always 1400 UTC should clear up any future concerns :) -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Ops Meetups Team - Meeting Reminder
UTC does not care about DST good people. Just a reminder for those of us who do observe DST that the meeting is one hour earlier than previously: http://www.worldtimebuddy.com/?pl=1&lid=5128581,100,4699066,5746545&h=5128581 Meeting is always 1400 UTC should clear up any future concerns :) -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org > On Nov 8, 2016, at 06:53, Tom Fifield wrote: > > By my clock, this is in about an hour from now. > >> On 05/11/16 08:26, Chris Morgan wrote: >> You're right, my mistake. 9am Tuesday (for me)! See you then >> >> Chris >> >> Sent from my iPhone >> >>> On Nov 4, 2016, at 8:07 PM, Saverio Proto wrote: >>> >>> Hello Chris, >>> >>> Thanks for clarify the meeting is Tuesday :) >>> >>> I have a doubt about the time. >>> reading here: >>> https://wiki.openstack.org/wiki/Ops_Meetups_Team >>> >>> Tuesdays at 14:00 UTC >>> >>> On November the 8th: >>> It is 15:00 Zurich/Rome/Paris time >>> 9:00 AM NYC time >>> >>> because UTC never changes in summer and winter, so it used to be 10:00 >>> in NYC and 16:00 in Europe but now it all shifted 1 hour earlier. >>> >>> makes sense ? I dont know why you wrote 13:00 UTC, was it a mistake ? >>> >>> thank you >>> >>> Saverio >>> >>> >>> >>> 2016-11-04 19:25 GMT+01:00 Chris Morgan : >>>> Hello All, >>>> >>>> When we met last week in Barcelona (some of us) I think there was >>>> consensus around picking up our normal Tuesday IRC meetings as of next >>>> Tuesday, which I see now is the 8th. Someone mentioned the 7th during that >>>> meeting, though, so I'd like to clarify. Are we all in agreement for >>>> Tuesday >>>> 8th? What time? It is normally 10AM my time which will be 13:00 UTC on the >>>> 8th. >>>> >>>> By the way, the Barcelona hosting offer has been updated with possible week >>>> day slots, see >>>> https://etherpad.openstack.org/p/ops-meetup-venue-discuss-spring-2017 >>>> >>>> Regards >>>> >>>> Chris >>>> >>>>> On Tue, Oct 4, 2016 at 10:45 AM, Saverio Proto wrote: >>>>> >>>>> sorry I will not make it today >>>>> saverio >>>>> >>>>> >>>>> Il 04 ott 2016 4:42 PM, "Melvin Hillsman" ha >>>>> scritto: >>>>>> >>>>>> #openstack-operators >>>>>> >>>>>> -- >>>>>> Melvin Hillsman >>>>>> Ops Technical Lead >>>>>> OpenStack Innovation Center >>>>>> mrhills...@gmail.com <mailto:centermrhills...@gmail.com> >>>>>> phone: (210) 312-1267 >>>>>> mobile: (210) 413-1659 >>>>>> Learner | Ideation | Belief | Responsibility | Command >>>>>> http://osic.org >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> On 10/4/16, 9:39 AM, "Edgar Magana" wrote: >>>>>>> >>>>>>> Hello All, >>>>>>> >>>>>>> I am trying to join the meeting but I am not sure which IRC channel you >>>>>>> use. >>>>>>> >>>>>>> Edgar >>>>>>> >>>>>>> On 10/4/16, 5:30 AM, "Matt Van Winkle" wrote: >>>>>>> >>>>>>> Hey Ops Meetup folks, >>>>>>> >>>>>>> Gentle reminder that the meeting is in about 1.5 hours at 14:00 UTC. >>>>>>> I won’t be able to make it because of an all-day planning meeting. >>>>>>> Hopefully, Tom will be around to help manage the chaos. Edgar should be >>>>>>> joining to talk about the UC sessions and how we can help with those. >>>>>>> Also, >>>>>>> we need to further refine the schedule. I’ve made some notes in the >>>>>>> ehterpad [1] >>>>>>> >>>>>>> >>&
[Openstack-operators] [openstack-operators] Barcelona Retrospective
Hey everyone, Keeping with some activities I see others doing, thought it would be great to get some feedback from everyone here - https://etherpad.openstack.org/p/ops-barcelona-retrospective -- Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com mobile: (210) 413-1659 office: (210) 312-1267 Learner | Ideation | Belief | Responsibility | Command http://osic.org ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [openstack-operators] Ops Midcycle March 2017 Results
Hey everyone! We want to thank all of you who took time to submit your opinion for the upcoming Ops Mid-cycle in March 2017. We left the decision up to the community - as we should - and you all decided that Milano, Italy is it! Results are as follows: [ http://doodle.com/poll/e7fcfhsf4s8cupyi ] Tokyo, JapanMilano, Italy Yes 58 66 Ifneedbe 10 7 No 55 50 We had quite a bit more response than from the last meetup and are glad to see the growth in participation. We will be providing more details in the coming days so please be sure to be on the lookout for updates. Thank you all again on behalf of the Ops Meetups Team! https://wiki.openstack.org/wiki/Ops_Meetups_Team -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com mobile: (210) 413-1659 office: (210) 312-1267 Learner | Ideation | Belief | Responsibility | Command http://osic.org ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [User-committee] UC Bylaws Changes - Approved!
Boom! On Tue, Dec 6, 2016 at 10:26 AM, Edgar Magana wrote: > Team, > > > > I am gladly informing you that the BoD has just approved our proposal to > change the OpenStack Bylaws: > > https://docs.google.com/document/d/1QmLOeseAkjBWM_ > TXsUeKBErNaSHnuZp81II0T71ARfo/edit?usp=sharing > > > > This is a huge step to bring the visibility and empowerment that we were > looking to have from the OpenStack User perspective. > > > > I want to thank you all! You made this possible because of your support, > guidance and motivation. > > > > We have a lot of more work to do but for today we can take a break and > celebrate. > > > > OpenStack User Committee, > > Shilla Saebi, Jon Proulx and Edgar Magana > > ___ > User-committee mailing list > user-commit...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee > > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [recognition] AUC Recognition WG is being disbanded
Great job everyone! I am glad to be counted amongst such great people. On Tue, Dec 6, 2016 at 12:45 PM, Shamail Tahir wrote: > Hi everyone, > > The team worked diligently over the last few months to identify user > contributions that benefit the entirety of the OpenStack community and to > help get these contributors recognized as Active User Contributors (AUC). > The AUC is the constituency for the User Committee and will be the voting > body for User Committee elections in the future. > > With the approval of the updated by-laws and User Committee charter > earlier today[1], we have completed our objective of defining AUC. The > User Committee members can take ownership of any future adjustments that > need to be made to the AUC criteria[2]. > > Our wiki[3] has been updated to reflect our status and I have also > submitted a patch to cancel our weekly team meeting[4]. > > I would like to thank everyone on the team for staying focused on the > objective and helping us achieve this important task! > > AUC Recognition WG participants: > carolbarrett > dabukalam > dc_mattj > emagana > jproulx > maishsk (co-chair) > meganr > mrhillsman > pfreund > pholland > rstarmer > shamail (co-chair) > swdevangel > > > [1] http://lists.openstack.org/pipermail/user-committee/ > 2016-December/001480.html > [2] http://www.slideshare.net/ShamailXD/openstack-auc-overview > [3] https://wiki.openstack.org/wiki/AUCRecognition > [4] https://review.openstack.org/#/c/407637/ > > -- > Thanks, > Shamail Tahir > t: @ShamailXD > tz: Eastern Time > > ___ > 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
Re: [Openstack-operators] VM monitoring suggestions
We have been using influxdata's influxdb, telegraf, and kapacitor with grafana for visualization [1]. You do not have to install telegraf in the VM to gather data on them however will need telegraf on the compute node and more than likely have to use some coding of telegraf to get what you want out. There is also a tool called netdata [2] which may suffice for what you are wanting to collect. Robert and Joe seem to have a sense of what you want and may offer the best option. [1] http://influxdata.com [2] https://github.com/firehol/netdata On Sun, Dec 11, 2016 at 7:33 PM, Đức Nguyễn Công < nguyencongduc3...@gmail.com> wrote: > Using Collectd virt plugin is a good point to start, for more information, > you can read this article https://community.rackspace.com/products/f/25/t/ > 6800 > Using Ceilometer with MongoDB for monitoring services will give heavy load > because of too many api requests (tesed with Kilo and Liberty). We used > Ceilometer only for alert perpose. > In newer cycle, you shoud have a try MaaS or Ceilomer + Gnocchi + Aodh. > > > 2016-11-21 15:17 GMT+07:00 Van Leeuwen, Robert : > >> >>I know that ceilometer may be an option, but I believe operators use >> all kind of tools for their own ressource usage monitoring. So what do you >> people use? >> >> >> >> >>(For this use case, we're looking for something that can be used >> without installing an agent in the VM, which makes it impossible to get a >> VM's load metric. I would be satisfied with cpu/memory/network/io metrics >> though.) >> >> >> >> >> >> Although I’d like to re-evaluate ceilometer at some point we currently >> use something very simple with the infra we already had in place. >> >> >> >> We use the collectd libvirt plugin and push the metrics to graphite. >> >> https://collectd.org/wiki/index.php/Plugin:virt >> >> >> >> If you use the following format you get the instance uuid in the metric >> name: >> >> HostnameFormat "hostname uuid" >> >> >> >> The output of those graphite keys is not exactly what we want (IIRC you >> get hostname_uuid instead of hostname.uuid) >> >> We rewrite it a bit with carbon-(c-)relay daemon to something more usable >> so you get: >> >> computenode.libvirt.UUID.metrics >> >> >> >> We made a grafana dashboard where you can select the uuid and get the >> stats of the instance. >> >> >> >> Pros: >> >> * Simple, just needs collectd on compute nodes >> >> * Graphite scales (with the proper setup) >> >> >> >> Cons: >> >> * No tenant-id in the metric name (I guess with some scripting you can >> make a mapping-tree in graphite) >> >> * No metrics in Horizon. (We still have to make some time to integrate >> these metrics into horizon but that should be doable.) >> >> * Just instance metrics nothing else >> >> >> >> Cheers, >> >> Robert van Leeuwen >> >> ___ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> > > > -- > Best Regards! > > Duc, Nguyen Cong > Skype: ducn...@hotmail.com > Phone: (+84)948309446 <+84%2094%20830%2094%2046> > Site: http://ducnc.github.io/ > > ___ > 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
Re: [Openstack-operators] [User-committee] User Committee IRC Meeting - Monday Dec 19th
Thanks for the update! On Thu, Dec 15, 2016 at 3:30 PM, Edgar Magana wrote: > Dear UC Community, > > > > Due to the Holidays! I would like to cancel next week UC IRC meeting. We > will resume our session on Jan 2nd. Same channel, time and Agenda will be > posted here: > > *https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee > <https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee>* > > > > Happy Holidays! > > > > User Committee OpenStack > > Jon, Shilla and Edgar > > ___ > User-committee mailing list > user-commit...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee > > -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Ops Meetups - paragraphs for the annual report
Great idea. Here is my 0.02 Ops Meetups Team came together early in the year with the hope of the Operator community driving mid-cycles and summit planning. In just over six months the Ops Meetups Team has successfully planned, organized, and executed a mid-cycle and the Barcelona Ops Summit. The Ops Meetups Team operates openly having IRC meetings Tuesdays at 15:00 UTC in #openstack-operators. Currently in the organization and execution phase of the Ops Spring Mid-cycle the team looks forward to growing and working together in 2017. -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org > On Jan 1, 2017, at 21:08, Tom Fifield wrote: > > Hi Ops Meetups Team, > > Each year, the Foundation produces an annual report summarising the > activities from the year before. It would be great to one or two paragraphs > from the ops meetups team describing how we work and some info about the past > and upcoming events. > > Anyone game? > > > Regards, > > > Tom > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Ops Meetups - paragraphs for the annual report
Doh, I misread paragraph or two as sentence or two. Will add more words. -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org > On Jan 2, 2017, at 08:01, Lauren Sell wrote: > > Thanks, Melvin! I think this looks really good. I would just recommend adding > a couple of sentences about the high level value of the events for those who > are not familiar. What were the goals and outcomes of the operator’s > gatherings, what was the impact to the larger community and software? > > >> On Jan 2, 2017, at 1:38 AM, Melvin Hillsman wrote: >> >> Great idea. Here is my 0.02 >> >> Ops Meetups Team came together early in the year with the hope of the >> Operator community driving mid-cycles and summit planning. In just over six >> months the Ops Meetups Team has successfully planned, organized, and >> executed a mid-cycle and the Barcelona Ops Summit. The Ops Meetups Team >> operates openly having IRC meetings Tuesdays at 15:00 UTC in >> #openstack-operators. Currently in the organization and execution phase of >> the Ops Spring Mid-cycle the team looks forward to growing and working >> together in 2017. >> >> -- >> Melvin Hillsman >> Ops Technical Lead >> OpenStack Innovation Center >> mrhills...@gmail.com >> phone: (210) 312-1267 >> mobile: (210) 413-1659 >> Learner | Ideation | Belief | Responsibility | Command >> http://osic.org >> >>> On Jan 1, 2017, at 21:08, Tom Fifield wrote: >>> >>> Hi Ops Meetups Team, >>> >>> Each year, the Foundation produces an annual report summarising the >>> activities from the year before. It would be great to one or two paragraphs >>> from the ops meetups team describing how we work and some info about the >>> past and upcoming events. >>> >>> Anyone game? >>> >>> >>> 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 > smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Ops Meetups - paragraphs for the annual report
Sorry for the delay. Here are more words :) with need for revision/changes and plugging in the number of attendees and companies representing during this past Fall mid-cycle in NYC; unfortunately I do not have but believe Foundation may. I am no scholar but hope this is a good starting point. One signficant accomplishment in 2016 was the creation of the Ops Meetups Team. The Ops Meetups Team came together early in the year with the hope of the operator community driving mid-cycle and Ops Summit planning. In just over six months the Ops Meetups Team has successfully planned, organized, and executed a mid-cycle and the Barcelona Ops Summit. During the Fall 2016 Ops Mid-cycle held in New York City and hosted by Bloomberg, we had approximately [# of attendees] attendees representing at least [# of companies] companies. Sessions ignited discussions ranging from the physical hardware layer to NFV and containerizing the OpenStack control plane to orchestrating with Kubernetes. While not only focusing on the underlying technology driving all the *aaS, folks talked about the supporting cast of logging, monitoring, and alerting tools, and much more. Attending these events afford Operators the opportunity to come away being energized with new creative ways to address their day-to-day requirements and exciting ideas about how they can offer more to themselves and their stakeholders using the robust OpenStack platform. OpenStack at large benefits as the community of operators, engineers, application developers, and end users spend quality time with each other sustaining the wave of momentum for OpenStack's future. The Ops Meetups Team operates openly having IRC meetings Tuesdays at 15:00 UTC in #openstack-operators. Currently in the organization and execution phase of the Ops Spring Mid-cycle, March 15-16 2017 in Milan, Italy, the team looks forward to growing and working together. On Mon, Jan 2, 2017 at 8:57 AM, Tim Bell wrote: > > > Can we also include a credit for the company that hosted the mid-cycle? > > > > Tim > > > > *From: *Lauren Sell > *Date: *Monday, 2 January 2017 at 15:01 > *To: *Melvin Hillsman > *Cc: *openstack-operators > *Subject: *Re: [Openstack-operators] Ops Meetups - paragraphs for the > annual report > > > > Thanks, Melvin! I think this looks really good. I would just recommend > adding a couple of sentences about the high level value of the events for > those who are not familiar. What were the goals and outcomes of the > operator’s gatherings, what was the impact to the larger community and > software? > > > > > > On Jan 2, 2017, at 1:38 AM, Melvin Hillsman wrote: > > > > Great idea. Here is my 0.02 > > > Ops Meetups Team came together early in the year with the hope of the > Operator community driving mid-cycles and summit planning. In just over six > months the Ops Meetups Team has successfully planned, organized, and > executed a mid-cycle and the Barcelona Ops Summit. The Ops Meetups Team > operates openly having IRC meetings Tuesdays at 15:00 UTC in > #openstack-operators. Currently in the organization and execution phase of > the Ops Spring Mid-cycle the team looks forward to growing and working > together in 2017. > > -- > > *Melvin Hillsman* > > Ops Technical Lead > OpenStack Innovation Center > > mrhills...@gmail.com > phone: (210) 312-1267 > mobile: (210) 413-1659 > Learner | Ideation | Belief | Responsibility | Command > > http://osic.org > > > On Jan 1, 2017, at 21:08, Tom Fifield wrote: > > Hi Ops Meetups Team, > > Each year, the Foundation produces an annual report summarising the > activities from the year before. It would be great to one or two paragraphs > from the ops meetups team describing how we work and some info about the > past and upcoming events. > > Anyone game? > > > 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 > > > -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] What would you like in Pike?
Hey everyone, I am hoping to get a dialogue started to gain some insight around things Operators, Application Developers, and End Users would like to see happen in Pike. If you had a dedicated environment, dedicated team, and freedom to choose how you deployed, new features, older features, enhancements, etc, and were not required to deal with customer/client tickets, calls, and maintenances, could keep a good feedback loop between your team and the upstream community of any project, what would like to make happen or work on hoping the next release of OpenStack had/included/changed/enhanced/removed…? Kind regards, -- Melvin Hillsman Ops Technical LeadOpenStack Innovation Center mrhillsman@gmail.comphone: (210) 312-1267mobile: (210) 413-1659Learner | Ideation | Belief | Responsibility | Command http://osic.org ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] What would you like in Pike?
Very welcome Matt! Kind regards, -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org On 1/16/17, 11:03 AM, "Matt Riedemann" wrote: On 1/12/2017 7:30 PM, Melvin Hillsman wrote: > Hey everyone, > > > > I am hoping to get a dialogue started to gain some insight around things > Operators, Application Developers, and End Users would like to see > happen in Pike. If you had a dedicated environment, dedicated team, and > freedom to choose how you deployed, new features, older features, > enhancements, etc, and were not required to deal with customer/client > tickets, calls, and maintenances, could keep a good feedback loop > between your team and the upstream community of any project, what would > like to make happen or work on hoping the next release of OpenStack > had/included/changed/enhanced/removed…? > > I just wanted to say thanks for starting this thread. I often wonder what people would like to see the Nova team prioritize because we don't get input from the product work group or Foundation really on big ticket items so we're generally left to prioritizing work on our own each release. -- Thanks, Matt Riedemann ___ 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
Re: [Openstack-operators] What would you like in Pike?
> they find solutions to problems that arise. >> >> https://docs.google.com/presentation/d/1LKxQx4Or4qOBwPQbt4jA >> ZncGCLlk_Ez8ZRB_bGp19JU/edit?usp=sharing >> >> >> >> ___ >> OPERATOR INTERVIEWS: DEPLOYMENT AT PRODUCTION >> Why this research matters: >> Deployment has been consistently identified as an issue by operators >> during the user survey and impacts both adoption and operations of >> OpenStack. We wanted to do a deep dive with operators to identify the >> specific issues impacting deployment. >> >> Study design: >> A series of 1:1 interviews that included included discussions around >> organizations, tools, workflows and pain points associated with deploying >> OpenStack. >> >> https://docs.google.com/presentation/d/14UerMR4HrXKP_0NE_C-W >> J16YQFzgetL1Tmym9FNFzpY/edit?usp=sharing >> >> >> ___ >> OPERATOR USABILITY: OPENSTACKCLIENT >> Why this research matters: >> Consistency across projects has been identified as an issue in the user >> survey. >> >> Study design: >> This usability study, conducted at the OpenStack Austin Summit, observed >> 10 operators as they attempted to perform standard tasks in the OpenStack >> client. >> >> https://docs.google.com/presentation/d/1cBUJuLL9s7JQppVlDBBJ >> MrNNpfqwdkHyfZFuwY6lNgM/edit#slide=id.g1a8df2eaf2_1_0 >> >> >> >> >> >> >> >> >> >> >> On Tue, Jan 17, 2017 at 10:07 AM, Jonathan Proulx >> wrote: >> >>> >>> What Tim said :) >>> >>> my ordering: >>> >>> 1) Preemptable Instances -- this would be huge and life changing I'd >>>give up any other improvements to get this. >>> >>> 2) Deeper utilization of nested projects -- mostly we find ways to >>>mange with out this but it would be great to have. >>> >>>A) to allow research groups (our internal fiscal/administrative >>>divisions) to sub divide quota allocations accordinf to their own >>>priorities on a self serve basis (provided proper RBAC configs) >>>B) to answer show back questions more easily. Currently with flat >>>projects individual research groups have multiple openstack >>>projects, by convention we mange to usually be able to aggregaet >>>them in reporting, but deing able to show susage by a parent and >>>all it 's childeren woudl be very useful >>> >>> 3) Quota improvements -- this is important but we've learned to deal >>>with it >>> >>> -Jon >>> >>> On Sat, Jan 14, 2017 at 10:10:40AM +, Tim Bell wrote: >>> :There are a couple of items which have not been able to make it to the >>> top priority for recent releases which would greatly simplify our day to >>> day work with the users and make the cloud more flexible. The background >>> use cases are described in https://openstack-in-productio >>> n.blogspot.fr/2016/04/resource-management-at-cern.html >>> : >>> : >>> :- Quota management improvements >>> : >>> :oManual interventions are often required to sync the current usage >>> with the OpenStack view >>> : >>> :oNested projects are now in Keystone but is limited support in >>> other projects for the end user benefit, such as delegation of quota for >>> sub-projects >>> : >>> :- Nova pre-emptible instances (https://review.openstack.org/ >>> #/c/104883/) to give spot market functionality >>> : >>> :oWe want to run our cloud at near 100% utilisation but this >>> requires rapid ejection of lower priority VMs >>> : >>> :That having been said, I also fully support key priorities currently >>> being worked on such as cells v2 and placement. >>> : >>> :Tim >>> : >>> :From: Melvin Hillsman >>> :Date: Friday, 13 January 2017 at 02:30 >>> :To: openstack-operators >>> :Subject: [Openstack-operators] What would you like in Pike? >>> : >>> :Hey everyone, >>> : >>> :I am hoping to get a dialogue started to gain some insight around >>> things Operators, Application Developers, and End Users would like to see >>> happen in Pike. If you had a dedicated environment, dedicated team, and >>> freedom to choose how you deployed, new features, older features, >>> enhancements, etc, and were not required to deal w
[Openstack-operators] OsOps Reboot
Good day everyone, As operators we would like to reboot the efforts started around OsOps. Initial things that may make sense to work towards are starting back meetings, standardizing the repos (like having a lib or common folder, READMEs include release(s) tool works with, etc), increasing feedback loop from operators in general, actionable work items, identifying teams/people with resources for continuous testing/feedback, etc. We have got to a great place so let's increase the momentum and maximize all the work that has been done for OsOps so far. Please visit the following link [ https://goo.gl/forms/eSvmMYGUgRK901533 ] to vote on day of the week and time (UTC) you would like to have OsOps meeting. And also visit this etherpad [ https://etherpad.openstack.org/p/osops-meeting ] to help shape the initial and ongoing agenda items. Really appreciate you taking time to read through this email and looking forward to all the great things to come. Also we started an etherpad for brainstorming around how OsOps could/would function; very rough draft/outline/ideas right now again please provide feedback: https://etherpad.openstack.org/p/osops-project-future -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] OsOps Reboot
Thanks for the feedback Curtis! I have updated the form to include a short answer form at the top for typing in custom day/time combinations; Mon-Fri 15:00-22:00 UTC for example. On Sat, Jan 21, 2017 at 10:24 AM, Curtis wrote: > On Thu, Jan 19, 2017 at 11:32 PM, Melvin Hillsman > wrote: > > Good day everyone, > > > > As operators we would like to reboot the efforts started around OsOps. > > Initial things that may make sense to work towards are starting back > > meetings, standardizing the repos (like having a lib or common folder, > > READMEs include release(s) tool works with, etc), increasing feedback > loop > > from operators in general, actionable work items, identifying > teams/people > > with resources for continuous testing/feedback, etc. > > > > We have got to a great place so let's increase the momentum and maximize > all > > the work that has been done for OsOps so far. Please visit the following > > link [ https://goo.gl/forms/eSvmMYGUgRK901533 ] to vote on day of the > week > > and time (UTC) you would like to have OsOps meeting. And also visit this > > etherpad [ https://etherpad.openstack.org/p/osops-meeting ] to help > shape > > the initial and ongoing agenda items. > > The poll is a little unusual. :) I don't know how you are going to get > a good vote out of it. I would like vote for any time from 15:00 UTC > to 22:00 UTC from Mon - Fri but not 15:00 UTC on Weds b/c I have > another meeting at that time. I did put in a vote in your form as > well, but just kind of put in a single UTC time slot on each day of > the week. > > Thanks, > Curtis. > > > > > Really appreciate you taking time to read through this email and looking > > forward to all the great things to come. > > > > Also we started an etherpad for brainstorming around how OsOps > could/would > > function; very rough draft/outline/ideas right now again please provide > > feedback: https://etherpad.openstack.org/p/osops-project-future > > > > > > -- > > Kind regards, > > > > Melvin Hillsman > > Ops Technical Lead > > OpenStack Innovation Center > > > > mrhills...@gmail.com > > phone: (210) 312-1267 > > mobile: (210) 413-1659 > > http://osic.org > > > > Learner | Ideation | Belief | Responsibility | Command > > > > ___ > > OpenStack-operators mailing list > > OpenStack-operators@lists.openstack.org > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > > -- > Blog: serverascode.com > -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [openstack-operators][openstack-ansible] Optioanal services documentation for Newton
Hey Salman, Maybe this will help - http://docs.openstack.org/project-deploy-guide/openstack-ansible/newton/ - the documentation has changed a bit since Newton ( http://docs.openstack.org/developer/openstack-ansible/newton/ ) On Sun, Jan 22, 2017 at 2:12 PM, Salman Toor wrote: > Hi, > > Wondering can someone help me pointing the openstack-ansible (Newton) > guide for optional services? I have found for Mitaka but not for Newton. > > Basically looking for a similar link for Newton (Following is for Mitaka): > > http://docs.openstack.org/developer/openstack-ansible/ > mitaka/install-guide/configure.html > > Regards.. > Salman. > > > > PhD, Scientific Computing > Researcher, IT Department, > Uppsala University. > Senior Cloud Architect, > SNIC. > Cloud Application Expert, > UPPMAX. > salman.t...@it.uu.se > <https://mail.uu.se/owa/redir.aspx?REF=m0Eyh6bAe3V0K5jcrZeIkUVJw4_716jYUS9Yd1fJMFOsyyE71yXTCAFtYWlsdG86c2FsbWFuLnRvb3JAaXQudXUuc2U.> > http://www.it.uu.se/katalog/salto690 > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] OsOps Reboot
Unfortunately I had not requested travel for the PTG but plan to be at the mid cycle should nothing change. -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org > On Jan 23, 2017, at 18:27, Matt Fischer wrote: > > Will there be enough of us at the PTG for an impromptu session there as well? > >> On Mon, Jan 23, 2017 at 9:18 AM, Mike Dorman wrote: >> +1! Thanks for driving this. >> >> >> >> >> >> From: Edgar Magana >> Date: Friday, January 20, 2017 at 1:23 PM >> To: "m...@mattjarvis.org.uk" , Melvin Hillsman >> >> >> >> Cc: OpenStack Operators >> Subject: Re: [Openstack-operators] OsOps Reboot >> >> >> I super second this! Yes, looking forward to amazing contributions there. >> >> >> >> Edgar >> >> >> >> From: Matt Jarvis >> Reply-To: "m...@mattjarvis.org.uk" >> Date: Friday, January 20, 2017 at 12:33 AM >> To: Melvin Hillsman >> Cc: OpenStack Operators >> Subject: Re: [Openstack-operators] OsOps Reboot >> >> >> >> Great stuff Melvin ! Look forward to seeing this move forward. >> >> >> >> On Fri, Jan 20, 2017 at 6:32 AM, Melvin Hillsman >> wrote: >> >> Good day everyone, >> >> >> >> As operators we would like to reboot the efforts started around OsOps. >> Initial things that may make sense to work towards are starting back >> meetings, standardizing the repos (like having a lib or common folder, >> READMEs include release(s) tool works with, etc), increasing feedback loop >> from operators in general, actionable work items, identifying teams/people >> with resources for continuous testing/feedback, etc. >> >> >> >> We have got to a great place so let's increase the momentum and maximize all >> the work that has been done for OsOps so far. Please visit the following >> link [ https://goo.gl/forms/eSvmMYGUgRK901533 ] to vote on day of the week >> and time (UTC) you would like to have OsOps meeting. And also visit this >> etherpad [ https://etherpad.openstack.org/p/osops-meeting ] to help shape >> the initial and ongoing agenda items. >> >> >> >> Really appreciate you taking time to read through this email and looking >> forward to all the great things to come. >> >> >> >> Also we started an etherpad for brainstorming around how OsOps could/would >> function; very rough draft/outline/ideas right now again please provide >> feedback: https://etherpad.openstack.org/p/osops-project-future >> >> >> >> -- >> >> Kind regards, >> >> Melvin Hillsman >> Ops Technical Lead >> OpenStack Innovation Center >> >> mrhills...@gmail.com >> phone: (210) 312-1267 >> mobile: (210) 413-1659 >> http://osic.org >> >> Learner | Ideation | Belief | Responsibility | Command >> >> >> ___ >> 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 >> > smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Plus One...need I say more?
Calling all Operators! help us plan the mid-cycle. *Please add topics to https://etherpad.openstack.org/p/MIL-ops-meetup <https://etherpad.openstack.org/p/MIL-ops-meetup>or +1 those that are already there that you are interested in; even if you are not attending.For each session that makes the cut we will need volunteer moderators. Moderators simply facilitate a conversation.* *Please be sure you +1 at least 3 to 5 sessions while you take time to view the etherpad, your vote(s) count!!!* The Ops Meetups team meets regularly on IRC at 15:00 UTC on Tuesdays in #openstack-operators. More information about the team is here : https://wiki.openstack.org/ wiki/Ops_Meetups_Team and weekly agendas are posted here : https://etherpad.openstack.org/p/ops-meetups-team -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Ops Midcycle - Seating Limited Reserve Your Spot!
Good day everyone, We have been hard at work planning another great Ops Mid-cycle! Seating is limited so you will want to rush over to - https://opsmidcycle_march2017.eventbrite.com - to reserve your spot. Also, we still want your feedback on the sessions and we need your +1s. We are in the process of writing the agenda and therefore it is very important you get your vote in now on a session or two or all. You can find the planning etherpad here - https://etherpad.openstack.org/p/MIL-ops-meetup REMEMBER! Even if you are not attending in person, you can still vote! We want to hear from you. ***Note***: This event assumes OpenStack ops knowledge and is _not_ appropriate for beginners, or a place to learn about OpenStack. The event contains relatively few 'presentations' and is mostly a discussion-style event. To find other OpenStack events in your area, please visit www.openstack.org/events. Kind regards, -- Melvin Hillsman Ops Technical LeadOpenStack Innovation Center mrhillsman@gmail.comphone: (210) 312-1267mobile: (210) 413-1659Learner | Ideation | Belief | Responsibility | Command http://osic.org ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: [openstack-dev] Supporting our global community
In case you missed it. -- Forwarded message -- From: Jonathan Bryce Date: Sun, Jan 29, 2017 at 12:34 PM Subject: [openstack-dev] Supporting our global community To: foundat...@lists.openstack.org, "OpenStack Development Mailing List (not for usage questions)" , commun...@openstack.org OpenStack is a global open source community. The OpenStack Foundation serves members in 180 countries focused on advancing the capabilities and accessibility of open infrastructure everywhere. We fundamentally believe diversity and collaboration are a powerful force for innovation, and it has been amazing to see the product of tens of thousands of people around the world over the last 6+ years. Lauren, Mark and I disagree with the executive order issued by President Trump that targets individuals from 7 countries. The order restricts the travel and movement of people in a discriminatory way that results in a restriction on access to talent and ideas. It is still unclear how the policies will play out and be enforced, but we will be watching, advocating for and supporting our community members to the best of our ability. This executive order will not impact the governance of the Foundation or the way the community operates globally. We will continue to support user groups and community members that are active in the seven countries named by the executive order, alongside our 120+ user groups around the world. However, we have two scheduled events in the United States within the next six months that will attract a global audience: the PTG (Project Teams Gathering) in Atlanta, Feb 20-24, a smaller event that will bring together hundreds of upstream contributors, and the OpenStack Summit in Boston, May 8-11, our larger event that happens every six months. This executive order could impact some community members' ability to travel to Atlanta and Boston, but unfortunately it is too late at this point to change the location of these events. The following three OpenStack Summits, however, are now scheduled to occur outside of the United States. The next Summit will be in November 2017 in Sydney, Australia and we are working to finalize the details so we can announce the following two Summit locations soon. We’ve already heard from one community member, Mohammed Naser, who is concerned that his plans to travel from Canada to Atlanta to attend the PTG may be restricted, simply because he a dual citizen of Canada and Iraq. Mohammed has been contributing code to OpenStack since 2011 and is the CEO and Founder of Vexxhost. Blocking his travel would serve no purpose and rob the community of a valuable contributor during an important event. If you are concerned about the impact or have any questions, please don't hesitate to reach out to me at jonat...@openstack.org. Political actions like this highlight the importance of our collective values. The Four Opens, the founding principles of our community, exist to ensure the free flow of talent and ideas, across geographic, national, organizational or other lines that might divide us. We believe in humanity. We believe in opportunity. We believe in the power of collaboration across borders, and we will continue to carry forward our mission. We also posted this online: https://www.openstack.org/ blog/2017/01/supporting-our-global-community/ Jonathan Bryce Mark Collier Lauren Sell __ 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 -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Operator Mid-cycle Moderator
Hey everyone, Thank you all for signing up to be moderators at the upcoming Operator Mid-cycle. I am sending this not only to you but to the ML at large in hopes that we get additional volunteers. Community: Please sign up if you are interested using the following etherpad - https://etherpad.openstack.org/p/MIL-ops-meetup And there is still time to suggest additional sessions and +1 or -1 existing sessions. Also remember that you do not have to be in attendance to have a voice here. We welcome you to participate in shaping the agenda even though you may not physically attend. Current Volunteer Moderators: What I learned after moderating my first session is that you have to continuously prod folks to discuss the current topic and after a moment or two the conversation will take on a life of its own; so should be pretty easy, especially if you just hand folks the mic (emagana). We have a moderation guide as well to assist you - https://wiki.openstack.org/wik i/Operations/Meetups#Moderators_Guide What I hope to accomplish with this email is that you 1) respond back confirming that you will or will not attend the mid-cycle, and 2) begin looking at the sessions <https://etherpad.openstack.org/p/MIL-ops-meetup> and brainstorm what the summaries for the sessions you are thinking about moderating should look like. You will want to think about primarily what the session will cover and the expected outcomes or success criteria; which can be as simple as providing at least 3 actionable items to those users/developers/projects/teams/groups/etc impacted by the session. Once we have a somewhat finalized agenda, I will send a follow up email so we can work to round out the summaries and get them out to the community. Thank you so much for your time. -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] OpenStack User Survey!
Hey everyone, Re-sending this, hopefully we can get a lot more folks to fill out the survey! " If you run OpenStack, please take a few minutes to respond to the latest User Survey or pass it along to your friends. This is the ninth survey, but if you're new what you can expect are: * a few basic questions—how and why do you work with OpenStack, what do you like about it, and where can we improve? (5-10mins) * a more detailed set of questions that helps us understand your cloud so we can provide feedback to development teams (10mins) The deadline to fill out the survey is February 20 at 23:59 UTC. Start the survey now: https://www.openstack.org/user-survey If you answered the survey last time, you won't need to start from scratch. Just log back in to update your deployment profile. All of the information you provide is confidential to the Foundation and User Committee and will be aggregated anonymously unless you specifically allow us to make it public. We’ll share the survey findings first with those who fill out the user survey, and with the community at next OpenStack Summit, May 8-11 in Boston https://www.openstack.org/summit/boston-2017/ " -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] OsOps Reboot
Hey everyone! I really appreciate the responses to the poll for the OsOps meeting and we have consensus on the time being Monday 1400 UTC. The time is not set in stone and as folks participate time will be adjusted to accommodate the majority; the meeting will be on February 27th, 2017. You can find the time within your local timezone using wordltimebuddy, for example http://www.worldtimebuddy.com/?pl=1&lid=100,1816670,5128581,2147714&h=100 We will be working from the following document - https://etherpad.openstack.org/p/osops-meeting - for the agenda and welcome everyone to add to/adjust/+1 it and invite a friend to the meeting; if you do not think something should be on the agenda comment, -1, or strikethrough. On Tue, Jan 24, 2017 at 11:23 AM, Edgar Magana wrote: > I do not think the PTG is the place for this session. However, if there > will be enough participation and you are already all over there, it maes > sense to get together. > > > > Edgar > > > > *From: *Matt Fischer > *Date: *Monday, January 23, 2017 at 4:27 PM > *To: *Mike Dorman > > *Cc: *OpenStack Operators > *Subject: *Re: [Openstack-operators] OsOps Reboot > > > > Will there be enough of us at the PTG for an impromptu session there as > well? > > > > On Mon, Jan 23, 2017 at 9:18 AM, Mike Dorman wrote: > > +1! Thanks for driving this. > > > > > > *From: *Edgar Magana > *Date: *Friday, January 20, 2017 at 1:23 PM > *To: *"m...@mattjarvis.org.uk" , Melvin Hillsman < > mrhills...@gmail.com> > > > *Cc: *OpenStack Operators > *Subject: *Re: [Openstack-operators] OsOps Reboot > > > > I super second this! Yes, looking forward to amazing contributions there. > > > > Edgar > > > > *From: *Matt Jarvis > *Reply-To: *"m...@mattjarvis.org.uk" > *Date: *Friday, January 20, 2017 at 12:33 AM > *To: *Melvin Hillsman > *Cc: *OpenStack Operators > *Subject: *Re: [Openstack-operators] OsOps Reboot > > > > Great stuff Melvin ! Look forward to seeing this move forward. > > > > On Fri, Jan 20, 2017 at 6:32 AM, Melvin Hillsman > wrote: > > Good day everyone, > > > > As operators we would like to reboot the efforts started around OsOps. > Initial things that may make sense to work towards are starting back > meetings, standardizing the repos (like having a lib or common folder, > READMEs include release(s) tool works with, etc), increasing feedback loop > from operators in general, actionable work items, identifying teams/people > with resources for continuous testing/feedback, etc. > > > > We have got to a great place so let's increase the momentum and maximize > all the work that has been done for OsOps so far. Please visit the > following link [ https://goo.gl/forms/eSvmMYGUgRK901533 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_eSvmMYGUgRK901533&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=qvIhIoN0dOM5nWbCYOcJ0KN7fxQ-YV-X49j-AEjyqJI&s=alnlXDgvLn4JwSH2BxBgGhHdaLQ0dA0QFse0OmbkjLY&e=> > ] to vote on day of the week and time (UTC) you would like to have OsOps > meeting. And also visit this etherpad [ https://etherpad.openstack. > org/p/osops-meeting > <https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_osops-2Dmeeting&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=qvIhIoN0dOM5nWbCYOcJ0KN7fxQ-YV-X49j-AEjyqJI&s=9waKkQ4VAfwG7loT9xlE2Rj6bJQpPooOBv6YESGfi4o&e=> > ] to help shape the initial and ongoing agenda items. > > > > Really appreciate you taking time to read through this email and looking > forward to all the great things to come. > > > > Also we started an etherpad for brainstorming around how OsOps could/would > function; very rough draft/outline/ideas right now again please provide > feedback: https://etherpad.openstack.org/p/osops-project-future > <https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_osops-2Dproject-2Dfuture&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=qvIhIoN0dOM5nWbCYOcJ0KN7fxQ-YV-X49j-AEjyqJI&s=lKeYaJZMzld5eqlOxQ2a7cS7iQB2tzxzDlR5TKkYi2w&e=> > > > > -- > > Kind regards, > > Melvin Hillsman > Ops Technical Lead > OpenStack Innovation Center > > mrhills...@gmail.com > phone: (210) 312-1267 > mobile: (210) 413-1659 > http://osic.org > <https://urldefense.proofpoint.com/v2/url?u=http-3A__osic.org&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ
Re: [Openstack-operators] [openstack-operators][telecom-nfv] Milan Meetup
Thanks for the update Curtis! On Wed, Feb 15, 2017 at 8:45 AM, Curtis wrote: > Hi, > > I just wanted to note that I won't be able to go to the Milan meetup, > just took my name off the moderators list. Apologies, just bad timing. > Getting to Milan is hard from Edmonton, I have to snowshoe to Red Deer > to take a dogsled to Calgary. ;) > > In our telecom-nfv meeting last week we had people from the LCOO and > Massively Distributed group, and there was no one in that meeting that > was attending either, to the best of my knowledge. Perhaps that will > change by the meetup. > > However, I see a fair number of +1s and a mention of the "planned > maintenance" feature in the etherpad, so there may very well be enough > people with NFV responsibilities at the meetup for a good NFV session, > I'm not sure. I believe Shintaro will be there and is usually involved > in NFV related items. :) > > I just wanted to let you all know, as I have not been able to make the > weekly operators meetings. > > Thanks, > Curtis. > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [User-committee] User Committee elections
Thank you to everyone who voted, the election committee, and the others who ran. I consider it an honor and privilege and am looking forward to the coming days. -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org > On Feb 17, 2017, at 18:10, Matt Jarvis wrote: > > Hi All > > I'm very pleased to announce the results of the first User Committee > elections, which closed at 21.59UTC on the 17th February 2017. > > The two candidates elected to the User Committee are Melvin Hillsman and > Shamail Tahir. > > Congratulations to Melvin and Shamail, I know they will both do an excellent > job in representing our community. > > Thank you to the other candidates who participated, and to everyone who > voted. > > Full results of the poll can be found at > http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4ec37f2d06428110. > > Matt > > ___ > User-committee mailing list > user-commit...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Instances are not creating after adding 3 additional nova nodes
Since the error was with scheduling you will want to modify the config for nova to show verbose output, try to create another instance, and check for the uuid and/or requestid of the creation attempt in the log - nova-scheduler.log I would turn verbose logging off right after you get a failed attempt to schedule as well since they logs can grow quickly. On Mon, Feb 20, 2017 at 12:56 AM, Saverio Proto wrote: > Well, > I have no idea from this log file. Trying to make nova-compute more > verbose if you dont find anything in the logs > > Saverio > > 2017-02-20 7:50 GMT+01:00 Anwar Durrani : > > > > On Thu, Feb 16, 2017 at 1:44 PM, Saverio Proto > wrote: > >> > >> openstack server show uuid > > > > > > Hi Saverio, > > > > I have investigated and progressed the case as per your saying, i got to > > know that instance was supposed to be launched on one of the nova node, > > where i dig and tried find out log as you mentioned, following output i > have > > seen as below : > > > > tail -f /var/log/nova/nova-compute.log > > > > 2017-02-20 10:40:19.318 5365 WARNING nova.compute.manager > > [req-34fa4448-061d-44ad-b6e9-6ff0d1fd072f - - - - -] While synchronizing > > instance power states, found 4 instances in the database and 0 instances > on > > the hypervisor. > > > > and > > > > other log where i have found following : > > > > tail -f /var/log/nova/nova-manage.log > > > > 2017-02-15 16:42:42.896 115003 TRACE nova File > > "/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 34, in > > sleep > > > > 2017-02-15 16:42:42.896 115003 TRACE nova hub.switch() > > > > 2017-02-15 16:42:42.896 115003 TRACE nova File > > "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 294, in > switch > > > > 2017-02-15 16:42:42.896 115003 TRACE nova return > self.greenlet.switch() > > > > 2017-02-15 16:42:42.896 115003 TRACE nova File > > "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 346, in > run > > > > 2017-02-15 16:42:42.896 115003 TRACE nova self.wait(sleep_time) > > > > > > Thanks > > > > > > > > -- > > Thanks & regards, > > Anwar M. Durrani > > +91-9923205011 > > > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] OSOps Reboot
Hey everyone, Just a friendly reminder about OSOps meeting on Monday February 27th, 1400UTC in #openstack-operators Please be sure to review the etherpad - https://etherpad.openstack.org/p/osops-meeting - and add agenda items or comment on existing ones. -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [User-committee] User Committee IRC Meeting - Monday Feb 13th
Thanks for the reminder Leong! Edgar I provided comments as requested; they are on the document itself. On Thu, Feb 23, 2017 at 7:02 PM, Edgar Magana wrote: > UC Members, > > > > Do not forget to prepare your feedback on the Product WG proposal for the > Forum. We need to internally approve it before we move it to the next phase. > > > > Thanks, > > > > Edgar > > > > *From: *"Yih Leong, Sun." > *Date: *Thursday, February 23, 2017 at 9:34 AM > *To: *Edgar Magana > *Cc: *"user-commit...@lists.openstack.org" openstack.org>, OpenStack Operators openstack.org>, "openst...@lists.openstack.org" < > openst...@lists.openstack.org> > *Subject: *Re: [User-committee] User Committee IRC Meeting - Monday Feb > 13th > > > > Hi, > > > > As discussed in previous UC meeting, can I also ask UC members to review > the proposal [1] on how Product WG can help to facilitate the Forum? > > > > [1] https://docs.google.com/presentation/d/1jTlO4UdNjc5cOKboeCNhLDEdttazW > WlDgNxxulUrPNg/edit > <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_presentation_d_1jTlO4UdNjc5cOKboeCNhLDEdttazWWlDgNxxulUrPNg_edit&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=cBERgAwwqBoi9v4fccj2CnXDrO9Sz3J8osE2y4wnK3s&s=jMpCSWIFPU4eXi_qaz_kYxYRBDaeJyQ4e6LbtrNvqwI&e=> > > > > Thanks! > > Leong. > > > > > > > > > > On Thu, Feb 23, 2017 at 9:15 AM, Edgar Magana > wrote: > > Dear UC Community, > > > > Our next UC IRC meeting is scheduled for this Monday Feb 27th at 1900 UTC > in (freenode) #openstack-meeting. > > > > Agenda: > > - Welcome UC elected members: Shamail and Melvin > > - Review previous action items > > - Board + TC + UC meeting in Boston (March 8-9, 2017) > > - Open agenda > > > > Thanks, > > > > Edgar > > > ___ > User-committee mailing list > user-commit...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_user-2Dcommittee&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=cBERgAwwqBoi9v4fccj2CnXDrO9Sz3J8osE2y4wnK3s&s=dwG3LgXzdve7SnE-sUr_Es_o42-edKrJe3jhJ4R60ks&e=> > > > -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Freenode Security Notification
Noticed this message this morning from Freenode so in case you missed it: "christel (christel@freenode/staff/exherbo.christel): [Global Notice] Hi all, Cloudflare has announced that a bug may have caused disclosure of data, sent via CF, to third parties, further info can be found at https://blog.cloudflare.com/ | freenode uses CF for CDN, while we have not received any reports indicating that we are affected, we urge webchat users in particular to consider changing their passwords! Thank you." -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: Operators Mid-cycle Moderator
Hey everyone, Thank you all for signing up to be moderators at the upcoming Operator Mid-cycle. I am sending this not only to you but to the ML at large in hopes that we get additional volunteers. *OpenStack Community:* Please sign up if you are interested in moderating using the following etherpad - https://etherpad.openstack.org/p/MIL-ops-meetup And * there is still time to suggest additional sessions and +1 or -1 existing sessions*. Also remember that *you do not have to be in attendance to have a voice here*. We welcome you to participate in shaping the agenda even though you may not physically attend. *Current Volunteer Moderators:* If you have not already, be sure to take a look at the moderator's guide - https://wiki.openstack.org/wiki/Operations/Meetups#Moderators_Guide What I hope to accomplish with this email is that you 1) respond back confirming that you will or will not attend the mid-cycle if you have not already confirmed, and 2) the agenda is just about done and some names have been added to sessions already. If you do not feel comfortable with a session you have been assigned, go ahead and change. If you see an open session and would like to moderate it, feel free to add your name. I created an etherpad for each session on the agenda and dropped in a template on each one - https://etherpad.openstack.org/p/MIL-ops-moderator- template - please be sure to start working out the details of the session. *I encourage each moderator to use this thread to ask any questions and reach out to the community at large and projects related to the session you are moderating.* I am looking forward to seeing all of you at the mid-cycle and thank you so much for your time. -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [openstack-operators] [osops] Meeting
Hey everyone, Just a friendly reminder about OSOps meeting on today at 1400UTC in #openstack-operators Please be sure to review the etherpad - https://etherpad.openstack.org/p/ osops-meeting - and add agenda items or comment on existing ones. -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Upcoming Ops Midcycle
Hey everyone, If you have been getting previous emails then you are aware the midcycle is quickly approaching; March 15th and 16th! *T**here is still time offer feedback for existing sessions*. Also remember that *you do not have to be in attendance to have a voice here*. We welcome you to participate in shaping the dialogue even though you may not physically attend. Below you will find all the etherpads for each session and there are no hard and fast rules so feel free to throw as many ideas in there as you can think of. Please also *encourage other Operators, End-Users, Application Developers, Developers, everyone you know who can offer some value to participate*. https://etherpad.openstack.org/p/MIL-ops-openstack-on-containers https://etherpad.openstack.org/p/MIL-ops-containers-on-openstack https://etherpad.openstack.org/p/MIL-ops-logging-and-monitoring https://etherpad.openstack.org/p/MIL-ops-ceph-and-cephfs https://etherpad.openstack.org/p/MIL-ops-baremetal https://etherpad.openstack.org/p/MIL-ops-upgrades-patches-packaging https://etherpad.openstack.org/p/MIL-ops-config-management https://etherpad.openstack.org/p/MIL-ops-keystone-and-authentication https://etherpad.openstack.org/p/MIL-ops-inventory-and-fleet-management https://etherpad.openstack.org/p/MIL-ops-live-migration https://etherpad.openstack.org/p/MIL-ops-security https://etherpad.openstack.org/p/MIL-ops-scaling-and-tuning https://etherpad.openstack.org/p/MIL-ops-deployment-methods https://etherpad.openstack.org/p/MIL-ops-rabbitmq-pitfalls-ha https://etherpad.openstack.org/p/MIL-ops-dbaas-with-trove https://etherpad.openstack.org/p/MIL-ops-do-not-do https://etherpad.openstack.org/p/MIL-ops-osops https://etherpad.openstack.org/p/MIL-ops-fault-injection-and-remediation https://etherpad.openstack.org/p/MIL-ops-migration-onboarding-end-user-experience https://etherpad.openstack.org/p/MIL-ops-ux-horizon-cli https://etherpad.openstack.org/p/MIL-ops-cellsv2 https://etherpad.openstack.org/p/MIL-ops-neutron https://etherpad.openstack.org/p/MIL-ops-cinder-rolling-upgrade https://etherpad.openstack.org/p/MIL-ops-overview-of-auc https://etherpad.openstack.org/p/MIL-ops-uc https://etherpad.openstack.org/p/MIL-ops-capacity-management https://etherpad.openstack.org/p/MIL-ops-manila https://etherpad.openstack.org/p/MIL-ops-telco-nfv -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [user-committee] [openstack-operators] [openstack-community] [osops] Team Bi-Weekly Meeting Summary
Apologies for the delay, We had a great reboot meeting! The previous and upcoming agendas can be found at the following: http://etherpad.openstack.org/p/osops-meeting *The next meeting is 3/13 1400UTC in #openstack-meeting-5* We focused on quite a few things and are looking to start hashing out some actionable work around the discussions in the coming days, below is just a snapshot of some items: - Establish structure/pluggability around the "when approved" repo (tool creators should only have to worry about the logic of what the tool will do - common tasks imported via libs) - Work towards stable/release branches and tags approach (starting with stable/newton being ocata was just released not long ago) - Standardizing in general (an example is every tool requires a README so at a glance user is aware of pertinent information about the tool) - Documentation assistance (it is not about writing but reviewing what is currently in place and filing a bug at a minimum, creating a patch is always encouraged) - Reviewing and contributing user stories - https://github.com/openstack/openstack-user-stories (this is significant as users have to back the stories for work to be potentially allocated; the more +1s/reviews a story gets, more likely it is seen as valuable work) *We hope to see you in the next meeting, invite a friend or two or 10 and come with your opinions, grievances, ideas, and dreams!* -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [osops] Milan Ops Midcycle - OSOps Session
Here's the etherpad for the OSOps session at the Ops Midcycle: https://etherpad.openstack.org/p/MIL-ops-osops I have added some points to consider during the session and would love for you to add new topics and/or comments on the existing ones; even if you are not attending. Also a reminder to participate in the session brainstorming for the Forum! https://wiki.openstack.org/wiki/Forum/Boston2017 -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] OpenStack Operators Milan - Neutron Session
Agree with you on this Edgar and it deserves further discussion. We discussed this a week ago or so now amongst Ops Meetup Team and again, I think we should discuss further; I am not saying what is right or wrong. -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org > On Mar 13, 2017, at 12:33, Edgar Magana wrote: > > Hello Chris, > > I totally understand your position. Believe me, without vendors support we > wouldn’t even have an Ops Meetup as successful as we have currently. > My email was an open question to all Operators about the format of the > sessions. It was clear that the company that you work for was requested an > updated and not the other way around. > > Thanks, > > Edgar > > From: Christoph Andreas Torlinsky > Date: Monday, March 13, 2017 at 10:30 AM > To: Edgar Magana > Cc: "randy.perry...@dell.com" , > "OpenStack-operators@lists.openstack.org" > > Subject: Re: [Openstack-operators] OpenStack Operators Milan - Neutron Session > > Hey Edgar, i'm going because we run our NuageX Dev/Test on OpenStack, so we > are also 'operators', eating our own product > and contributing back to OpenStack with anything we hit, and I'm also an avid > user of OpenStack myself, > hope that clears it up a bit, I'm not going to Vendor pitch or do marketing, > for that we have other venues. > > We are also one of the sponsors as it happens along with Bloomberg, Intel and > others, > which is also a nice thing, to contribute into the community. > > all the best, > > c > > > Christoph Andreas Torlinski > > christ...@nuagenetworks.net > > On 13 March 2017 at 17:21, Edgar Magana wrote: > WOW! Something has changed from previous Ops Meet-ups. I remember clearly > that we (Operators), wanted to have a free-from-vendors environment and it > seems that now we want them to come and provide updates on their offerings. > I think vendors have plenty opportunities to show their features and demos, > for instance the Summits and OpenStack Days around the world. > > Thanks, > > Edgar > > From: Christoph Andreas Torlinsky > Date: Monday, March 13, 2017 at 10:11 AM > To: "randy.perry...@dell.com" > Cc: "OpenStack-operators@lists.openstack.org" > > Subject: Re: [Openstack-operators] OpenStack Operators Milan - Neutron Session > > I'll be there from Nuage Networks, as far as I know. > > > > > Christoph Andreas Torlinski > > christ...@nuagenetworks.net > > On 9 March 2017 at 13:36, wrote: > Here is the etherpad for the Neutron Session in Milan > https://etherpad.openstack.org/p/MIL-ops-neutron > > Please add to it anything you would like to cover. > > Also will anyone from SDN Vendors be there? Please come and provide a 5 > minute update to your offering. > > Thank You > > Randy Perryman > Technical Staff, Cloud Architect > Certified OpenStack Administrator > > Dell EMC | OpenSource Solutions Group > office + 01 603 249 7710 > mobile +01 603 321 5611 > email randy.perry...@dell.com > http://www.dell.com/cloud > > Please consider the environment before printing this email. > > Confidentiality Notice | This e-mail message, including any attachments, is > for the sole use of the intended recipient(s) and may contain confidential or > proprietary information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, > immediately contact the sender by reply e-mail and destroy all copies of the > original message. > > > > ___ > 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 smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Milan Ops Midcycle
Hey everyone, I want to send a big thank you to everyone who participated in the Midcycle! To our sponsors we appreciate you making a venue, food, and all the other logistics that went into making the event a success. Thank you to every moderator who dealt with me nagging them about their sessions and getting some actionable items out of their discussions; I have one more request coming :) Additionally thank you to all the companies who sent their folks to the Midcycle: Enter, Bloomberg, Nuage Networks, Intel, Cloudbase, Switch, and OpenStack And to you folks who attended in person and remotely, we are very greatful that we sold every ticket, ate lots of Italian food, the courtyard side chats, networking, collaboration, and so much more. Be sure to communicate the value you got out of attending but most importantly let us work together outside of the Midcycle to accomplish what we can. Remember OSOps meeting in #openstack-meeting-5 on 03/27/17 at 1400 UTC -- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Boston Forum Brainstorming
Hey everyone! Please be aware of the following dates if you have not heard already. I know we mentioned this extensively at the Midcycle this week and yep, here we are again! Take note that the deadline for the brainstorming phase is fast approaching. March 20: end of brainstorming phase, opening of formal submission tool EOD April 2: deadline for topic submission April 10: publication of the schedule Take just a few moments to drop your thoughts in the etherpad(s) found at: https://wiki.openstack.org/wiki/Forum/Boston2017 In particular: https://etherpad.openstack.org/p/BOS-UC-brainstorming If you have any questions, reply back to this thread or reach out to any of us. -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: [Openstack] nova-network -> neutron migration docs and stories?
-- Forwarded message -- From: Joe Topjian Date: Fri, Mar 17, 2017 at 10:52 PM Subject: Re: [Openstack] nova-network -> neutron migration docs and stories? To: Andrew Bogott Cc: "openst...@lists.openstack.org" Hi Andrew, NeCTAR published a suite of scripts for doing a nova-network to neutron migration: https://github.com/NeCTAR-RC/novanet2neutron IIRC, another organization reported success with these scripts a few months ago on the openstack-operators list. I'm currently doing some trial runs and all looks good. I had to make some slight modifications to account for IPv6 and floating IPs, but the scripts are very simple and readable, so it was easy to do. I'll probably post those modifications to Github in the next week or two. We'll be doing the actual migration in May. Hope that helps, Joe On Fri, Mar 17, 2017 at 2:18 PM, Andrew Bogott wrote: > Googling for nova-network migration advice gets me a lot of hits but > many are fragmentary and/or incomplete[1][2] I know that lots of people > have gone through this process, though, and that there are probably as many > different solutions as there are migration stories. > > So: If you have done this migration, please send me links! Blog > posts, docpages that you found useful, whatever you have to offer. We have > lots of ideas about how to move forward, but it's always nice to not repeat > other people's mistakes. We're running Liberty with flat dhcp and floating > IPs. > > Thanks! > > -Andrew > > [1] https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNet > work/HowTo#How_to_test_migration_process > ' TODO - fill in the migration process script here' > > [2] https://www.slideshare.net/julienlim/openstack-nova-network- > to-neutron-migration-survey-results > Slide 4: 'Develop tools to facilitate migration.' Did they? > > ___ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac > k > Post to : openst...@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac > k > ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openst...@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: [Openstack] nova-network -> neutron migration docs and stories?
-- Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 Learner | Ideation | Belief | Responsibility | Command http://osic.org Begin forwarded message: > From: Tim Bell > Date: March 18, 2017 at 09:49:18 GMT+1 > To: Andrew Bogott > Cc: "openst...@lists.openstack.org" > Subject: Re: [Openstack] nova-network -> neutron migration docs and stories? > > Ricardo from CERN gave a talk in Barcelona about our experiences. > https://www.youtube.com/watch?v=54wp1yzC-d8 > > eBay was one of the first to migrate - > http://superuser.openstack.org/articles/ebay-in-production-migration-from-nova-network-to-neutron/ > > Tim > > From: joe > Date: Friday, 17 March 2017 at 22:52 > To: Andrew Bogott > Cc: "openst...@lists.openstack.org" > Subject: Re: [Openstack] nova-network -> neutron migration docs and stories? > > Hi Andrew, > > NeCTAR published a suite of scripts for doing a nova-network to neutron > migration: https://github.com/NeCTAR-RC/novanet2neutron > > IIRC, another organization reported success with these scripts a few months > ago on the openstack-operators list. > > I'm currently doing some trial runs and all looks good. I had to make some > slight modifications to account for IPv6 and floating IPs, but the scripts > are very simple and readable, so it was easy to do. I'll probably post those > modifications to Github in the next week or two. > > We'll be doing the actual migration in May. > > Hope that helps, > Joe > > > On Fri, Mar 17, 2017 at 2:18 PM, Andrew Bogott wrote: > Googling for nova-network migration advice gets me a lot of hits but many > are fragmentary and/or incomplete[1][2] I know that lots of people have gone > through this process, though, and that there are probably as many different > solutions as there are migration stories. > > So: If you have done this migration, please send me links! Blog posts, > docpages that you found useful, whatever you have to offer. We have lots of > ideas about how to move forward, but it's always nice to not repeat other > people's mistakes. We're running Liberty with flat dhcp and floating IPs. > > Thanks! > > -Andrew > > [1] > https://wiki.openstack.org/wiki/Neutron/MigrationFromNovaNetwork/HowTo#How_to_test_migration_process > ' TODO - fill in the migration process script here' > > [2] > https://www.slideshare.net/julienlim/openstack-nova-network-to-neutron-migration-survey-results > Slide 4: 'Develop tools to facilitate migration.' Did they? > > ___ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openst...@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > ___ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openst...@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Boston Forum - Formal Submission Now Open!
Hey everyone! We have made it to the next stage of the topic selection process for the Forum in Boston. Starting today, our submission tool is open for you to submit abstracts for the most popular sessions that came out of your brainstorming. *Please note that the etherpads are not being pulled into the submission tool and discussion around which sessions to submit are encouraged.* We are asking all session leaders to submit their abstracts at: http://forumtopics.openstack.org/ *before 11:59PM UTC on Sunday April 2nd!* We are looking for a good mix of project-specific, cross-project or strategic/whole-of-community discussions, and *sessions that emphasize collaboration between users and developers are most welcome!* We assume that anything submitted to the system has achieved a good amount of discussion and consensus that it is a worthwhile topic. After submissions close, a team of representatives from the User Committee, the Technical Committee, and Foundation staff will take the sessions proposed by the community and fill out the schedule. You can expect the draft schedule to be released on April 10th. Further details about the Forum can be found at: https://wiki.openstack.org/ wiki/Forum Regards, OpenStack User Committee ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Reminder -- Forum Topic Submission
Hey everyone, This is a friendly reminder that all proposed Forum session leaders must submit their abstracts at: http://forumtopics.openstack.org/ *before 11:59PM UTC on Sunday April 2nd!* Regards, TC/UC ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Boston Forum Reminder
Hey everyone, This is a friendly reminder that all proposed Forum session leaders must submit their abstracts at: http://forumtopics.openstack.org/ *before 11:59PM UTC on Sunday April 2nd!* Regards, TC/UC ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: [openstack-dev] Project Navigator Updates - Feedback Request
For those interested. -- Forwarded message -- From: Lauren Sell Date: Fri, Mar 24, 2017 at 11:57 AM Subject: [openstack-dev] Project Navigator Updates - Feedback Request To: "OpenStack Development Mailing List (not for usage questions)" < openstack-...@lists.openstack.org> Hi everyone, We’ve been talking for some time about updating the project navigator, and we have a draft ready to share for community feedback before we launch and publicize it. One of the big goals coming out of the joint TC/UC/Board meeting a few weeks ago[1] was to help better communicate ‘what is openstack?’ and this is one step in that direction. A few goals in mind for the redesign: - Represent all official, user-facing projects and deployment services in the navigator - Better categorize the projects by function in a way that makes sense to prospective users (this may evolve over time as we work on mapping the OpenStack landscape) - Help users understand which projects are mature and stable vs emerging - Highlight popular project sets and sample configurations based on different use cases to help users get started For a bit of context, we’re working to give each OpenStack official project a stronger platform as we think of OpenStack as a framework of composable infrastructure services that can be used individually or together as a powerful system. This includes the project mascots (so we in effect have logos to promote each component separately), updates to the project navigator, and bringing back the “project updates” track at the Summit to give each PTL/core team a chance to provide an update on their project roadmap (to be recorded and promoted in the project navigator among other places!). We want your feedback on the project navigator v2 before it launches. Please take a look at the current version on the staging site and provide feedback on this thread. http://devbranch.openstack.org/software/project-navigator/ Please review the overall concept and the data and description for your project specifically. The data is primarily pulled from TC tags[2] and Ops tags[3]. You’ll notice some projects have more information available than others for various reasons. That’s one reason we decided to downplay the maturity metric for now and the data on some pages is hidden. If you think your project is missing data, please check out the repositories and submit changes or again respond to this thread. Also know this will continue to evolve and we are open to feedback. As I mentioned, a team that formed at the joint strategy session a few weeks ago is tackling how we map OpenStack projects, which may be reflected in the categories. And I suspect we’ll continue to build out additional tags and better data sources to be incorporated. Thanks for your feedback and help. Best, Lauren [1] http://superuser.openstack.org/articles/community-leadership-charts- course-openstack/ [2] https://governance.openstack.org/tc/reference/tags/ [3] https://wiki.openstack.org/wiki/Operations/Tags __ 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 -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Boston Forum Submission Deadline!
Hey everyone, Please take time to *submit your proposals *from the etherpad(s) or any other place you have captured/brainstormed. This is a friendly reminder that all proposed Forum session leaders must submit their abstracts at: http://forumtopics.openstack.org/ *before 11:59PM UTC on Sunday April 2nd!* Regards, TC/UC ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] OSOps Meetings for April
Hey everyone, Just a friendly reminder that OSOps meetings for April will happen on Monday April 10th and April 24th at 1400UTC in #openstack-meeting-5 Please feel free to add to the agenda and invite 100 people :) https://etherpad.openstack.org/p/osops-meeting You can catch up on previous meeting notes/logs by visiting http://eavesdrop.openstack.org/meetings/osops -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Reminder User Committee Meeting
Hey everyone, User Committee will meet today in #openstack-meeting @ 1900UTC. If you have any requests for agenda items you can reply to this email or message any of the UC members via email as well as IRC - #openstack-uc -- Kind regards, OpenStack UC ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] UC Meeting 04/10/17 Cancelled
Hey everyone, Apologies for the late notice. We are cancelling the meeting today. We have moved to a weekly cadence with meetings being subject to new agenda items having to be proposed/added by the Friday before the meeting. In other words, for UC meeting scheduled for 04/17/17 agenda items will need to be proposed/added by this Friday 04/14/17 Thanks very much, OpenStack UC ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] about the R release name
This cracked me up! "Mountain Dew learned the hard way when 4 Chan took
control of a vote
<http://www.huffingtonpost.com/2012/08/13/4chan-mountain-dew_n_1773076.html>
to name a new flavor, and the joke was on Taylor Swift and VH1 when the
Internet chose a school for the deaf
<http://www.huffingtonpost.com/2012/10/02/taylor-swift-horace-mann-school-for-the-deaf-4chan-prank-contest_n_1932257.html>
as a concert location."
On Mon, Apr 10, 2017 at 4:11 PM, Matt Joyce wrote:
> +2
>
> On Mon, Apr 10, 2017 at 5:07 PM, Monty Taylor
> wrote:
>
>> On 04/10/2017 02:10 PM, Amrith Kumar wrote:
>>
>>> The naming is based on community input and there's good reason to
>>> believe that in this round of voting both of these values will get a low
>>> score.
>>>
>>> But, we could have a repeat of the Boaty McBoatface debacle 😊
>>>
>>
>> I would totally vote for OpenStack Boaty McBoatface. Maybe we can switch
>> from place names to names of the form "{foo}y Mc{foo}face" for all releases
>> after Z ...
>>
>>
>> https://www.nytimes.com/2016/03/22/world/europe/boaty-mcboat
>>> face-what-you-get-when-you-let-the-internet-decide.html?_r=0
>>>
>>> -amrith
>>>
>>> --
>>> Amrith Kumar
>>> amrith.ku...@gmail.com
>>>
>>>
>>> -Original Message-
>>>> From: Saverio Proto [mailto:ziopr...@gmail.com]
>>>> Sent: Monday, April 10, 2017 3:02 PM
>>>> To: OpenStack Operators
>>>> Subject: [Openstack-operators] about the R release name
>>>>
>>>> Hello Ops,
>>>>
>>>> I got the mail about the Poll for OpenStack R Release Naming
>>>>
>>>> I am shocked that there are proposed names like Raspberry or Root !
>>>>
>>>> Think about troubleshooting and searching on google:
>>>>
>>>> Openstack Raspberry "string of log file"
>>>>
>>>> The Raspberry or Root words are anti-google words that will pollute the
>>>> search with a lot of results from other context domain
>>>>
>>>> Please be smart when voting ! We need names that can identify easily the
>>>> releases when using search engines !!!
>>>>
>>>> thank you
>>>>
>>>> Saverio
>>>>
>>>> ___
>>>> 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
>
>
--
Kind regards,
Melvin Hillsman
Ops Technical Lead
OpenStack Innovation Center
mrhills...@gmail.com
phone: (210) 312-1267
mobile: (210) 413-1659
http://osic.org
Learner | Ideation | Belief | Responsibility | Command
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Ops Meetups Team Meeting Reminder
Hey everyone, Just a reminder that the meetups team will be meeting today 4/11 at 1500UTC Agenda: https://etherpad.openstack.org/p/ops-meetups-team https://www.worldtimebuddy.com/?qm=1&lid=100,1816670,2147714,4699066&h=100&date=2017-4-11&sln=15-16 https://www.worldtimebuddy.com/?qm=1&lid=100,2643743,5391959,2950159&h=100&date=2017-4-11&sln=15-16 -- Kind regards, Melvin Hillsman Ops Technical Lead OpenStack Innovation Center mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://osic.org Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: Feedback wanted on Technical Committee Vision
If you did not see this, please take time to review and comment. -- Forwarded message -- From: OpenStack Technical Committee Date: Thu, Apr 13, 2017 at 8:53 AM Subject: Feedback wanted on Technical Committee Vision To: mrhills...@gmail.com Your feedback wanted on the 2019 Technical Committee vision Hello OpenStackers! The OpenStack Technical Committee (TC) recently completed work on a draft for their 2019 vision. The purpose of the vision is to provide a positive view of what success for any group (in this case, the Technical Committee) looks like. We would like to get feedback from everyone in the community on the vision before finalizing it in May. We are asking community members to provide feedback anonymously by completing a Survey Gizmo survey[0]. Please visit the Survey Gizmo link to view and review the vision draft: http://www.surveygizmo.com/s3/3490299/TC-2019-Vision For questions about the vision draft process or where to send feedback, please contact OpenStack Technical Committee member Colette Alexander at colettealexan...@gmail.com. Thanks very much, -The OpenStack TC & Stewardship Working Group The vision draft can also be viewed in the goverance repository[1] and is open for review comments. [0] http://www.surveygizmo.com/s3/3490299/TC-2019-Vision [1] https://review.openstack.org/#/c/453262/ PO Box 1903 | Austin , TX 78767 US This email was sent to mrhills...@gmail.com. To ensure that you continue receiving our emails, please add us to your address book or safe list. manage your preferences (https://app.e2ma.net/app2/audience/signup/1812998/ 1771360/1090800480/) opt out (https://t.e2ma.net/optout/iog2q/mbxpbs?r= aHR0cHM6Ly9hcHAuZTJtYS5uZXQvYXBwMi9hdWRpZW5jZS9vcHRfb3V0LzE4 MTI5OTgvMTc3MTM2MC8xMDkwODAwNDgwLw==) using TrueRemove(r). Got this as a forward? Sign up (https://app.e2ma.net/app2/ audience/signup/1812998/1771360.28188512/) to receive our future emails. -- Kind regards, Melvin Hillsman OpenStack Engineer, Rackspace mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://rackspace.com Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Ops Team Meeting 042417 Canceled
Hey everyone, Apologies for the late notice. Unless someone can facilitate the ops team meeting we will have to cancel for today: http://eavesdrop.openstack.org/#OpenStack_OSOps_Team -- Kind regards, Melvin Hillsman OpenStack Engineer, Rackspace mrhills...@gmail.com phone: (210) 312-1267 mobile: (210) 413-1659 http://rackspace.com Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [Forum] Unanswered Requirements
Hey everyone, I would like to take the opportunity to open the discussion up for feedback from the community leading into the Boston Forum. *Session Description*: Collaborate/communicate around user stories, gap analysis, what fits in the current state of tech, prioritize what would have the greatest impact in reducing pain for users. Ideally we would like to discuss in this session successes and failures of the current state of our feedback loop. We should be able to identify patterns that fit within a larger system/process that we are able to iterate through as the way to get user requirements implemented into code. [1] Moving the conversation forward is the aim with the ultimate goal being the first iteration of a plan that can be implemented, and one that gathers data/insight consistently to make specific and relevant improvements. [1] https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Ops Meetup Team
Hey everyone, We have been having some great momentum since the Foundation enlisted a small group of operators to manage the Midcycle and to form the Ops Meetup Team. We have a few asks related to the teaml: 1. More people! We need more folks to participate in the team meetings and activities; the more the merrier. You do not have to be an "operator"; everyone is welcome! 2. Themed midcycle. In an effort to continue to ensure the midcycle is relevant, we would like feedback on if folks agree with the midcycle being themed. Basically wherever the midcycle is being held, contact some folks in the region and focus on content that is more relevant to the folks in the region. More information on the team can be found on the wiki[1]. Meeting day and time is Tuesdays @ 1500UTC in #openstack-operators. We will also have a session[2] in Boston around the team, its purpose, and some items to make decisions on; looking forward to seeing you all in Boston! [1] https://wiki.openstack.org/wiki/Ops_Meetups_Team [2] https://www.openstack.org/summit/boston-2017/summit-schedule /events/18935/openstack-operators-ops-meetup-team-catch-up -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Board Initiative: Strategy for Unanswered Requirements
Good morning everyone! If you are at the Summit and available at 9:50am please take time to join us in Room 104 at the Hynes Convention Center. Just a couple things to remember: Context: http://superuser.openstack.org/articles/community-leadership-charts-course-openstack/ Etherpad: https://etherpad.openstack.org/p/BOS-forum-unanswered-requirements -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] today ops meet up team meeting on IRC (2017-5-16)
Agreed, I know I am hella late with response but was afk catching up on things. On Tue, May 16, 2017 at 9:57 AM, Edgar Magana wrote: > Let’s cancel this week and resume the next one. > > > > Thanks, > > > > Edgar > > > > *From: *Chris Morgan > *Date: *Tuesday, May 16, 2017 at 7:17 AM > *To: *OpenStack Operators > *Subject: *[Openstack-operators] today ops meet up team meeting on IRC > (2017-5-16) > > > > Today's meeting is due in just under an hour. I can't make it due to > scheduling conflicts, could someone else chair? Or we could cancel given > the in-person meeting last wednesday in Boston. > > > > Chris > > > > -- > > Chris Morgan > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > -- -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: [openstack-dev] [nova] Boston Forum session recap - cinder ephemeral storage
-- Forwarded message -- From: Matt Riedemann Date: Thu, May 18, 2017 at 4:24 PM Subject: [openstack-dev] [nova] Boston Forum session recap - cinder ephemeral storage To: openstack-...@lists.openstack.org The etherpad for this session is here [1]. The goal for this session was figuring out the use cases for using Cinder as instance ephemeral storage and short/long-term solutions. This really came down to a single use case, which is as an operator I want to use Cinder for all of my storage needs, which means minimal local compute disk is used for VMs. We discussed several solutions to this problem which are detailed with pros/cons in the etherpad. We arrived at two solutions, one is short-term and one is long-term: 1. Short-term: provide a way to force automatic boot from volume in the API. John Griffith had a POC for doing this with flavor extra specs which are controlled by the admin and by default are not discoverable by the API user. There are downsides to this, like the fact that the API user isn't specifying BDMs but while their server is creating, they see a volume pop up in Horizon which they didn't expect (which is for their root disk) and since they don't want to be charged for it, they delete it - which makes the server go into ERROR state eventually (and is not retried). This just makes for a weird/bad user experience and it was unclear how to microversion this in the API so it's discoverable, plus it couples two complicated debt-ridden pieces of Nova code: flavor extra specs and block device mappings. It is, however, fairly simple to implement. 2. Long-term: write an image backend driver which is a proxy to Cinder. This would not require any changes to the API, it's all configurable per-compute, it would remove the need for the in-tree RBD/ScaleIO/LVM image backends, and open up support for all other Cinder volume drivers - plus we'd allow passing through a volume type via flavor extra spec in this case. This option, however, has no owner, and is dependent on working it into an area of the code that is very complicated and high technical debt right now (the libvirt imagebackend code). So while we all agreed we'd love to have this, it's not even really on the horizon. As a compromise on the short-term option, I suggested that we avoid using flavor extra specs to embed auto-BFV and instead put a new attribute directly on the flavor, e.g. is_volume_backed, or something like that. This would be in a microversion which makes it discoverable. Operators control the flavors so they can control which ones have this flag set, and could tie those flavors to host aggregates for compute hosts where they want to avoid local disk for ephemeral storage. The next step from this session is going to be fleshing out this idea into a spec which can be discussed for the Queens release, which would also include details on the alternatives in the etherpad and the pros/cons for each so we don't lose that information. Unless someone beats me to it, I think I'm signed up for writing this spec. [1] https://etherpad.openstack.org/p/BOS-forum-using-cinder-for- nova-ephemeral-storage -- Thanks, Matt -- Thanks, Matt __ 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 -- -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: [openstack-dev] [nova] Boston Forum session recap - searchlight integration
-- Forwarded message -- From: Matt Riedemann Date: Thu, May 18, 2017 at 4:21 PM Subject: [openstack-dev] [nova] Boston Forum session recap - searchlight integration To: openstack-...@lists.openstack.org Hi everyone, After previous summits where we had vertical tracks for Nova sessions I would provide a recap for each session. The Forum in Boston was a bit different, so here I'm only attempting to recap the Forum sessions that I ran. Dan Smith led a session on Cells v2, John Garbutt led several sessions on the VM and Baremetal platform concept, and Sean Dague led sessions on hierarchical quotas and API microversions, and I'm going to leave recaps for those sessions to them. I'll do these one at a time in separate emails. Using Searchlight to list instances across cells in nova-api The etherpad for this session is here [1]. The goal for this session was to explain the problem and proposed plan from the spec [2] to the operators in the room and get feedback. Polling the room we found that not many people are deploying Searchlight but most everyone was using ElasticSearch. An immediate concern that came up was the complexity involved with integrating Searchlight, especially around issues with latency for state changes and questioning how this does not redo the top-level cells v1 sync issue. It admittedly does to an extent, but we don't have all of the weird side code paths with cells v1 and it should be self-healing. Kris Lindgren noted that the instance.usage.exists periodic notification from the computes hammers their notification bus; we suggested he report a bug so we can fix that. It was also noted that if data is corrupted in ElasticSearch or is out of sync, you could re-sync that from nova to searchlight, however, searchlight syncs up with nova via the compute REST API, which if the compute REST API is using searchlight in the backend, you end up getting into an infinite loop of broken. This could probably be fixed with bypass query options in the compute API, but it's not a fun problem. It was also suggested that we store a minimal set of data about instances in the top-level nova API database's instance_mappings table, where all we have today is the uuid. Anything that is set in the API would probably be OK for this, but operators in the room noted that they frequently need to filter instances by an IP, which is set in the compute. So this option turns into a slippery slope, and is potentially not inter-operable across clouds. Matt Booth is also skeptical that we can't have a multi-cell query perform well, and he's proposed a POC here [3]. If that works out, then it defeats the main purpose for using Searchlight for listing instances in the compute API. Since sorting instances across cells is the main issue, it was also suggested that we allow a config option to disable sorting in the API. It was stated this would be without a microversion, and filtering/paging would still be supported. I'm personally skeptical about how this could be consider inter-operable or discoverable for API users, and would need more thought and input from users like Monty Taylor and Clark Boylan. Next steps are going to be fleshing out Matt Booth's POC for efficiently listing instances across cells. I think we can still continue working on the versioned notifications changes we're making for searchlight as those are useful on their own. And we should still work on enabling searchlight in the nova-next CI job so we can get an idea for how the versioned notifications are working by a consumer. However, any major development for actually integrating searchlight into Nova is probably on hold at the moment until we know how Matt's POC works. [1] https://etherpad.openstack.org/p/BOS-forum-using-searchlight -to-list-instances [2] https://specs.openstack.org/openstack/nova-specs/specs/pike/ approved/list-instances-using-searchlight.html [3] https://review.openstack.org/#/c/463618/ -- Thanks, Matt __ 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 -- -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: [openstack-dev] [nova] Boston Forum session recap - instance/volume affinity for HPC
-- Forwarded message -- From: Matt Riedemann Date: Thu, May 18, 2017 at 6:53 PM Subject: [openstack-dev] [nova] Boston Forum session recap - instance/volume affinity for HPC To: openstack-...@lists.openstack.org The etherpad for this session is here [1]. This was about discussing ways to achieve co-location or affinity for VMs and volumes for high-performance, and was spurred by an older dev list discussion (linked in the etherpad). This quickly grew into side discussions and it became apparent that at a high level we were talking about complicated solutions looking for a problem. That is also touched on a bit after the session in the dev ML [2]. The base use case is a user wants their server instance and volume located as close to each other as possible, ideally on the same compute host. We talked about ways to model a sort of "distance" attribute between resource providers in an aggregate relationship (in the placement sense of 'aggregate', not compute host aggregates in nova). This distance or nearness idea led down a path for how you define distance in a cloud, i.e. does 'near' mean the same host or rack or data center in a particular cloud? How are these values defined - would they be custom per cloud and if so, how is that discoverable/inter-operable for an end API user? It was noted that flavors aren't inter-operable either really, at least not by name. Jay Pipes has an older spec [3] about generic scheduling which could replace server groups, so this could maybe fall into that. When talking about this there are also private cloud biases, i.e. things people are willing to tolerate or expose to their users because they are running a private cloud. Those same things don't all work in a public cloud, e.g. mapping availability zones one-to-one for cinder-volume and nova-compute on the same host when you have hundreds of thousands of hosts. Then there are other questions about if/how people have already solved this using things like flavors with extra specs and host aggregates and the AggregateInstanceExtraSpecsFilter, or setting [cinder]cross_az_attach=False in nova.conf on certain hosts. For example, setup host aggregates with nova-compute and cinder-volume running on the same host, define flavors with extra specs that match the host aggregate metadata, and then charge more for those flavors as your HPC type. Or, can we say, use Ironic? It's clear that we don't have a good end-user story for this requirement, and so I think next steps for this are going to involve working with the public cloud work group [4] and/or product work group [5] (hopefully those two groups could work together here) on defining the actual use cases and what the end user experience looks like. [1] https://etherpad.openstack.org/p/BOS-forum-compute-instance- volume-affinity-hpc [2] http://lists.openstack.org/pipermail/openstack-dev/2017-May/116694.html [3] https://review.openstack.org/#/c/183837/ [4] https://wiki.openstack.org/wiki/PublicCloudWorkingGroup [5] https://wiki.openstack.org/wiki/ProductTeam -- Thanks, Matt __ 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 -- -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: [openstack-dev] [nova] Boston Forum session recap - claims in the scheduler (or conductor)
-- Forwarded message -- From: Matt Riedemann Date: Thu, May 18, 2017 at 7:55 PM Subject: [openstack-dev] [nova] Boston Forum session recap - claims in the scheduler (or conductor) To: openstack-...@lists.openstack.org The etherpad for this session is here [1]. The goal for this session was to inform operators and get feedback on the plan for what we're doing with moving claims from the computes to the control layer (scheduler or conductor). We mostly talked about retries, which also came up in the cells v2 session that Dan Smith led [2] and will recap later. Without getting into too many details, in the cells v2 session we came to a compromise on build retries and said that we could pass hosts down to the cell so that the cell-level conductor could retry if needed (even though we expect doing claims at the top will fix the majority of reasons you'd have a reschedule in the first place). During the claims in the scheduler session, a new wrinkle came up which is the hosts that the scheduler returns to the top-level conductor may be in different cells. So if we have two cells, A and B, with hosts x and y in cell A and host z in cell B, we can't send z to A for retries, or x or y to B for retries. So we need some kind of post-filter/weigher filtering such that hosts are grouped by cell and then they can be sent to the cells for retries as necessary. There was also some side discussion asking if we somehow regressed pack-first strategies by using Placement in Ocata. John Garbutt and Dan Smith have the context on this (I think) so I'm hoping they can clarify if we really need to fix something in Ocata at this point, or is this more of a case of closing a loop-hole? We also spent a good chunk of the session talking about overhead calculations for memory_mb and disk_gb which happens in the compute and on a per-hypervisor basis. In the absence of automating ways to adjust for overhead, our solution for now is operators can adjust reserved host resource values (vcpus, memory, disk) via config options and be conservative or aggressive as they see fit. Chris Dent and I also noted that you can adjust those reserved values via the placement REST API but they will be overridden by the config in a periodic task - which may be a bug, if not at least a surprise to an operator. We didn't really get into this during the forum session, but there are different opinions within the nova dev team on how to do claims in the controller services (conductor vs scheduler). Sylvain Bauza has a series which uses the conductor service, and Ed Leafe has a series using the scheduler. More on that in the mailing list [3]. Next steps are going to be weighing both options between Sylvain and Ed, picking a path and moving forward, as we don't have a lot of time to sit on this fence if we're going to get it done in Pike. As a side request, it would be great if companies that have teams doing performance and scale testing could help out and compare before (Ocata) and after (Pike with claims in the controller) results, because we eventually want to deprecate the caching scheduler but that currently outperforms the filter scheduler at scale because of the retries involved when using the filter scheduler, and which we expect doing claims at the top will fix. [1] https://etherpad.openstack.org/p/BOS-forum-move-claims-from- compute-to-scheduler [2] https://etherpad.openstack.org/p/BOS-forum-cellsv2-developer -community-coordination [3] http://lists.openstack.org/pipermail/openstack-dev/2017-May/116949.html -- Thanks, Matt __ 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 -- -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Fwd: [openstack-dev] [openstack-doc] [dev] What's up doc? Summit recap edition
-- Forwarded message -- From: Alexandra Settle Date: Fri, May 19, 2017 at 6:12 AM Subject: [openstack-dev] [openstack-doc] [dev] What's up doc? Summit recap edition To: "openstack-d...@lists.openstack.org" Cc: "OpenStack Development Mailing List (not for usage questions)" < openstack-...@lists.openstack.org> Hi everyone, The OpenStack manuals project had a really productive week at the OpenStack summit in Boston. You can find a list of all the etherpads and attendees here: https://etherpad.openstack.org/p/docs-summit As we all know, we are rapidly losing key contributors and core reviewers. We are not alone, this is happening across the board. It is making things harder, but not impossible. Since our inception in 2010, we’ve been climbing higher and higher trying to achieve the best documentation we could, and uphold our high standards. This is something to be incredibly proud of. However, we now need to take a step back and realise that the amount of work we are attempting to maintain is now out of reach for the team size that we have. At the moment we have 13 cores, of which none are full time contributors or reviewers. This includes myself. That being said! I have spent the last week at the summit talking to some of our leaders, including Doug Hellmann (cc’d), Jonathan Bryce and Mike Perez regarding the future of the project. Between myself and other community members, we have been drafting plans and coming up with a new direction that will hopefully be sustainable in the long-term. I am interested to hear your thoughts. I want to make sure that everyone feels that we’re headed in the right direction first and foremost. All of these action items are documented in this WIP etherpad: https://etherpad.openstack.org/p/doc-planning Some further highlights from the event… · The documentation team was represented by myself, Olga, and Alex Adamov for the Project Update: Documentation on the Monday. If you’d like to catch up with what we talked about, the video is available online now: https://www.youtube.com/watch?v=jcfbKxbpRvc The translation team PTL, Ian Choi, also had a session about getting more involved with the I18N team. You can view that video here: https://www.youtube.com/watch?v=ybFI4nez_Z8 · Ian and I also hosted the joint I18N and documentation onboarding session. We were visited by some friendly faces, and some new ones. Between Ian and myself, we discussed the documentation and translation workflows, and how to get involved (the mailing list, IRC channel, etc). Which was lots of fun :) we’d love to see more people there in the future, hopefully we’ll slowly get there! · This week I was focusing heavily on making the community aware that the documentation team was struggling to maintain contributors, but continuing with the same amount of work. This was a heavy conversation to be having, but it posed some really interesting questions to key leaders, and hopefully raised appropriate concerns. Ildiko and I hosted “OpenStack documentation: The future depends on all of us”. This was a really interesting session. I was able to pose to the group of attendees that the documentation team was struggling to maintain contributions. Major Hayden was kind enough to take notes during the session, you can find those here: https://etherpad.openstack.org/p/doc-future The project teams that came and represented their groups were interested in discussing the project-specific documentation (is living in the project’s repo tree the best place?) and voiced concerns I had otherwise not heard before. I recommend reading the notes to get a better idea :) · Kendall Nelson and Ildiko also hosted a session on the OpenStack Upstream Institute highlights. I recommend watching the video which is now live and available here: https://www.openstack.org/ videos/boston-2017/openstack-upstream-institute-highlights · One of the key takeaways from the summit was the session that I joint moderated with Melvin Hillsman regarding the Operations and Administration Guides. You can find the etherpad with notes here: https://etherpad.openstack.org/p/admin-ops-guides The session was really helpful – we were able to discuss with the operators present the current situation of the documentation team, and how they could help us maintain the two guides, aimed at the same audience. The operator’s present at the session agreed that the Administration Guide was important, and could be maintained upstream. However, they voted and agreed that the best course of action for the Operations Guide was for it to be pulled down and put into a wiki that the operators could manage themselves. We will be looking at actioning this item as soon as possible. These action items will free up the documentation team to become gate keepers and reviewers of documentation. Our key focus as a team will be on the tooling for the docs.openstack.o
Re: [Openstack-operators] Ops Meet-up Mexico City
Awesome! On Wed, Jun 14, 2017 at 9:58 AM, Edgar Magana wrote: > All the credit for the local team. Gloria is doing a fantastic job. > > Edgar > > On 6/13/17, 6:41 PM, "Chris Morgan" wrote: > > Fantastic. Great work, Sir! > > Chris > > Sent from my iPhone > > > On Jun 13, 2017, at 8:09 PM, Edgar Magana > wrote: > > > > Folks, > > > > I have good news. The time has been finally confirmed to be from > 10am to 6pm. We are good with the current Eventbrite. Let’s spread the word! > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www. > eventbrite.com_e_mexico-2Dcity-2Dopenstack-2Doperators-2Dmeetup- > 2Dtickets-2D34989052197&d=DwIFaQ&c=DS6PUFBBr_ > KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_ > wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=xOaimSbHde91i8WhkWV3MHJOsXWtBv > cIckOiseJiKvE&s=MP-3_-XT5e345N8CeYWxjYE6jYZXKzSVPLsAE9WGEHg&e= > > > > Edgar > > > > On 6/13/17, 9:02 AM, "Edgar Magana" > wrote: > > > > Folks, > > > >We have a problem. Today during the Ops IRC meeting, I mentioned > that the time for the sessions is from 10am to 6pm but I was wrong, the > place does not open until 11am. Yes, I know this is really bad. > >The local team is trying to have the place at 10am. I will notify > back a soon as we get a response. > > > >Thanks, > > > >Edgar > > > > > > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Turning TC/UC workgroups into OpenStack SIGs [all][uc]
Hi everyone, One of the areas identified as a priority by the Board + TC + UC workshop in March was the need to better close the feedback loop and make unanswered requirements emerge. Part of the solution is to ensure that groups that look at specific use cases, or specific problem spaces within OpenStack get participation from a wide spectrum of roles, from pure operators of OpenStack clouds, to upstream developers, product managers, researchers, and every combination thereof. In the past year we reorganized the Design Summit event, so that the design / planning / feedback gathering part of it would be less dev- or ops-branded, to encourage participation of everyone in a neutral ground, based on the topic being discussed. That was just a first step. In OpenStack we have a number of "working groups", groups of people interested in discussing a given use case, or addressing a given problem space across all of OpenStack. Examples include the API working group, the Deployment working group, the Public clouds working group, the Telco/NFV working group, or the Scientific working group. However, for governance reasons, those are currently set up either as a User Committee working group[1], or a working group depending on the Technical Committee[2]. This branding of working groups artificially discourages participation from one side to the others group, for no specific reason. This needs to be fixed. We propose to take a page out of Kubernetes playbook and set up "SIGs" (special interest groups), that would be primarily defined by their mission (i.e. the use case / problem space the group wants to collectively address). Those SIGs would not be Ops SIGs or Dev SIGs, they would just be OpenStack SIGs. While possible some groups will lean more towards an operator or dev focus (based on their mission), it is important to encourage everyone to join in early and often. SIGs could be very easily set up, just by adding your group to a wiki page, defining the mission of the group, a contact point and details on meetings (if the group has any). No need for prior vetting by any governance body. The TC and UC would likely still clean up dead SIGs from the list, to keep it relevant and tidy. Since they are neither dev or ops, SIGs would not use the -dev or the -operators lists: they would use a specific ML (openstack-sigs ?) to hold their discussions without cross-posting, with appropriate subject tagging. Not everything would become a SIG. Upstream project teams would remain the same (although some of them, like Security, might turn into a SIG). Teams under the UC that are purely operator-facing (like the Ops Tags Team or the AUC recognition team) would likewise stay as UC subteams. Comments, thoughts ? [1] https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Working_Groups_and_Teams [2] https://wiki.openstack.org/wiki/Upstream_Working_Groups -- Melvin Hillsman & Thierry Carrez ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Turning TC/UC workgroups into OpenStack SIGs [all][uc]
On Wed, Jun 21, 2017 at 10:44 AM, Shamail Tahir wrote: > Hi, > > In the past, governance has helped (on the UC WG side) to reduce > overlaps/duplication in WGs chartered for similar objectives. I would like > to understand how we will handle this (if at all) with the new SIG proposa? > Also, do we have to replace WGs as a concept or could SIG augment them? One > suggestion I have would be to keep projects on the TC side and WGs on the > UC side and then allow for spin-up/spin-down of SIGs as needed for > accomplishing specific goals/tasks (picture of a diagram I created at the > Forum[1]). > > I believe we still have WGs that overlap for specific objectives - like scalability - and having a Scalability SIG could be more efficient rather than the objective existing in multiple WGs who still have to gather resources to address the objective. Spin up/down can still happen though I think of a SIG as something that while it would spin down at some point, it may be quite some time before it does, depending on the special interest. > The WGs could focus on defining key objectives for users of a shared group > (market vertical like Enterprise or Scientific WG, horizontal function like > PWG) and then SIGs could be created based on this list to accomplish the > objective and spin-down. Similarly a project team could determine a need to > gather additional data/requirements or need help with a certain task could > also spin-up a SIG to accomplish it (e.g. updating an outdated docs set, > discussion on a specific spec that needs to be more thoroughly crafted, > etc.) > > I think SIGs like Documentation, Public Cloud, Scalability, make sense rather than being created to address a more specific objective. A WG could spin off from a SIG but does not seem reasonable for it to be the other way around since the idea behind a working group is to work on something specific - AUC Recognition - and then those members fold back into 0 or 1 SIG. I could be off but I get the feeling that WGs can come together and find commonality amongst each other within a SIG and get more accomplished/quicker aggregating resources around what they already share interest in. > Finally, how will this change impact the ATC/AUC status of the SIG members > for voting rights in the TC/UC elections? > Personally I think AUC could go to all members of the SIGs and ATC for those meeting the criteria but this may be a conversation to have between TC/UC where extra-ATC is provided as it does not seem fair, though fair may be irrelevant or relative, for UC elections to be wholly subjected to all SIG members and not TC elections. > > [1] https://drive.google.com/file/d/0B_yCSDGnhIbzS3V1b1lpZGpIaHBmc29S > aUdiYzJtX21BWkl3/ > > Thanks, > Shamail > > PS: I wish we had a single thread on this topic so discussions happening > on the various MLs could be cross referenced. > > On Wed, Jun 21, 2017 at 10:59 AM, Melvin Hillsman > wrote: > >> Hi everyone, >> >> One of the areas identified as a priority by the Board + TC + UC workshop >> in March was the need to better close the feedback loop and make unanswered >> requirements emerge. Part of the solution is to ensure that groups that >> look at specific use cases, or specific problem spaces within OpenStack get >> participation from a wide spectrum of roles, from pure operators of >> OpenStack clouds, to upstream developers, product managers, researchers, >> and every combination thereof. In the past year we reorganized the Design >> Summit event, so that the design / planning / feedback gathering part of it >> would be less dev- or ops-branded, to encourage participation of everyone >> in a neutral ground, based on the topic being discussed. That was just a >> first step. >> >> In OpenStack we have a number of "working groups", groups of people >> interested in discussing a given use case, or addressing a given problem >> space across all of OpenStack. Examples include the API working group, the >> Deployment working group, the Public clouds working group, the Telco/NFV >> working group, or the Scientific working group. However, for governance >> reasons, those are currently set up either as a User Committee working >> group[1], or a working group depending on the Technical Committee[2]. This >> branding of working groups artificially discourages participation from one >> side to the others group, for no specific reason. This needs to be fixed. >> >> We propose to take a page out of Kubernetes playbook and set up "SIGs" >> (special interest groups), that would be primarily defined by their mission >> (i.e. the use case / problem space the group wants to collectively >> address). Those SIGs would not be Ops
Re: [Openstack-operators] [openstack-dev] [all][tc][uc] Turning TC/UC workgroups into OpenStack SIGs
TC workgroup, led by a couple of devs, and is >> lacking app user input. Artificial barriers discourage people to join. >> Let's just call all of them SIGs. >> >> - the "Public Cloud WG" tries to cover an extremely important use case >> for all of OpenStack (we all need successful OpenStack public clouds). >> However, so far I've hardly seen a developer joining, because it's seen >> as an Ops group just trying to make requirements emerge. I want the few >> developers that OVH or CityCloud or other public clouds are ready to >> throw upstream to use the rebranded "Public Cloud SIG" as a rally point, >> to coordinate their actions. Because if they try to affect upstream >> separately, they won't go far, and we badly need them involved. >> >> Yes, it's mostly a rebranding exercise, but perception matters. >> Hope this clarifies, >> >> -- >> Thierry Carrez (ttx) >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib >> e >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > -- > Thanks, > Shamail Tahir > t: @ShamailXD > tz: Eastern Time > > __ > 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 > > -- -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs
rk groups are there that care about scaling? So rather than > have 5 work groups that all overlap on some level for a specific issue, > create a SIG for that specific issue so the people involved can work on > defining the specific problem and work to come up with a solution that can > then be implemented by the upstream development teams, either within a > single project or across projects depending on the issue. And once the > specific issue is resolved, close down the SIG. > Examples here would be things that fall under proposed community wide > goals for a release, like running API services under wsgi, py3 support, > moving policy rules into code, hierarchical quotas, RBAC "admin of admins" > policy changes, etc. Have a SIG that is comprised of people with different > roles (project managers, product managers, operators, developers, docs, QA) > that are focused on solving that one specific issue and drive it, and then > close it down once some completion criteria is met. > > A SIG possibly should continue to exist for something like scaling, as it will more than likely not have been created for a defined work dealing with scaling but rather scaling itself which a number of work items would come out of. That still doesn't mean you're going to get the attendance you need from > all parties. I don't know how you solve that one. People are going to work > on what they are paid to work on. Part of the resolution SIGs can assist with in getting folks to attend, getting paid or not, are a number of outcomes from SIGs, well thought out feature requests (PjMs), understanding of what should/should not/can/can not be done (DEVs), why it makes sense to resolve one or more should/can nots (OPs), resources to speed time to resolution (PrMs), single point of discussion (ALL), etc, etc. Possibly when folks see that rather than spending 100% of their resources on a work item that load can be shared and there is a simple way to determine so by participating in a SIG that will help as well. > > > -- > > Thanks, > > Matt > > > __ > 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 > -- -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] [ops-meetup-team] Meeting Reminder - 06/27/17 @ 1400 UTC
Ops Meetup Team Meeting June 27th, 2017 @ 1400UTC #openstack-operators Agenda (feel free to suggest/add to): - Review previous action items - Mexico City Midcycle (08/17) - APAC Midcycle (proposed) - Open Discussion Meeting etherpad: https://etherpad.openstack.org/p/ops-meetups-team Past meetings: http://eavesdrop.openstack.org/meetings/ops_meetup_team/ http://eavesdrop.openstack.org/meetings/ops_meetups_team/ ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [User-committee] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding
+1 Did not have a chance to draft a message but thanks for ops mention. On Jun 29, 2017 3:02 PM, "Amy Marrich" wrote: > First off it looks really sleek and I love the look! A few thoughts though > and I do realize it's just a mock up: > > 1) We have Sponsor just to pick one but don't have > Operators/Administrators and their feedback is a major contribution so > please don't leave them out. > 2) I would list the contributor types in alphabetical order that way no > group feels slighted, you can't help it if Use Cases are last it's just > that they start with a U vs Code which is a C. > 3) What if you would like to contribute in multiple ways? > > Resources are definitely still underdevelopment there but are they meant > to be broad applicable to all resources with more specialized one's visible > when you click on how you'd like to contribute? > > Amy (spotz) > > On Thu, Jun 29, 2017 at 2:03 PM, Mike Perez wrote: > >> Hello all, >> >> Wes has just took my ugly mock up of the contributor portal idea and >> came up with this [1]. >> >> Here’s what he said: >> >> "The idea is to help get potential contributors to the right place, >> using the outline Mike put together. Rather than sending people to a >> different page for each contribution type, users would be able to see >> what options are available all on this page. We’d send them to any >> necessary page(s) once they’ve gone through this quasi-wizard. Is this >> along the lines of what you were thinking? page 2 shows the view once >> you’ve clicked “Code” on page 1 (just in case that wasn’t super >> obvious) Thanks!” >> >> What do you all think? This does change things a bit of instead of the >> landing page being more obvious of a resource of links, it’s both for >> new and current contributors. Current contributors would hopefully be >> able to see the resource links below. >> >> Keep in mind that we will be working in the “Top 5 requested help” and >> as suggested by Clark, an option of “I don’t know where I want to >> start, but I want to help” kind of option. This would direct people to >> resources such as Upstream University, mentor program, low hanging >> fruit, that release priority idea I talked about earlier, etc. >> >> Personally I like it! >> >> >> [1] - https://www.dropbox.com/s/3q172qwfkik1ysd/contributor-port >> al.pdf?dl=0 >> >> — >> Mike Perez >> >> On June 27, 2017 at 13:48:36, Mike Perez (thin...@gmail.com) wrote: >> > Hello all, >> > >> > Every month we have people asking on IRC or the dev mailing list having >> interest in working >> > on OpenStack, and sometimes they're given different answers from >> people, or worse, >> > no answer at all. >> > >> > Suggestion: lets work our efforts together to create some common >> documentation so that >> > all teams in OpenStack can benefit. >> > >> > First it’s important to note that we’re not just talking about code >> projects here. OpenStack >> > contributions come in many forms such as running meet ups, identifying >> use cases (product >> > working group), documentation, testing, etc. We want to make sure those >> potential contributors >> > feel welcomed too! >> > >> > What is common documentation? Things like setting up Git, the many >> accounts you need >> > to setup to contribute (gerrit, launchpad, OpenStack foundation >> account). Not all >> > teams will use some common documentation, but the point is one or more >> projects will use >> > them. Having the common documentation worked on by various projects >> will better help >> > prevent duplicated efforts, inconsistent documentation, and hopefully >> just more >> > accurate information. >> > >> > A team might use special tools to do their work. These can also be >> integrated in this idea >> > as well. >> > >> > Once we have common documentation we can have something like: >> > 1. Choose your own adventure: I want to contribute by code >> > 2. What service type are you interested in? (Database, Block storage, >> compute) >> > 3. Here’s step-by-step common documentation to setting up Git, IRC, >> Mailing Lists, >> > Accounts, etc. >> > 4. A service type project might choose to also include additional >> documentation in that >> > flow for special tools, etc. >> > >> > Important things to note in this flow: >> > * How do you want to contribute? >> > * Here are **clear** names that identify the team. Not code names like >> Cloud Kitty, Cinder, >> > etc. >> > * The documentation should really aim to not be daunting: >> > * Someone should be able to glance at it and feel like they can finish >> things in five minutes. >> > Not be yet another tab left in their browser that they’ll eventually >> forget about >> > * No wall of text! >> > * Use screen shots >> > * Avoid covering every issue you could hit along the way. >> > >> > ## Examples of More Simple Documentation >> > I worked on some documentation for the Upstream University preparation >> that has received >> > excellent feedback meet close to these suggestions: >> > * IRC [1]
Re: [Openstack-operators] [User-committee] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding
Got it! Looks great! On Thu, Jun 29, 2017 at 4:58 PM, Mike Perez wrote: > Hey Melvin, > > Ah yes, I should’ve mentioned earlier that this is totally a POC. > There are lots missing, don’t worry! :) > > — > Mike Perez > > On June 29, 2017 at 13:47:14, Melvin Hillsman (mrhills...@gmail.com) > wrote: > > +1 > > > > Did not have a chance to draft a message but thanks for ops mention. > > > > On Jun 29, 2017 3:02 PM, "Amy Marrich" wrote: > > > > > First off it looks really sleek and I love the look! A few thoughts > though > > > and I do realize it's just a mock up: > > > > > > 1) We have Sponsor just to pick one but don't have > > > Operators/Administrators and their feedback is a major contribution so > > > please don't leave them out. > > > 2) I would list the contributor types in alphabetical order that way no > > > group feels slighted, you can't help it if Use Cases are last it's just > > > that they start with a U vs Code which is a C. > > > 3) What if you would like to contribute in multiple ways? > > > > > > Resources are definitely still underdevelopment there but are they > meant > > > to be broad applicable to all resources with more specialized one's > visible > > > when you click on how you'd like to contribute? > > > > > > Amy (spotz) > > > > > > On Thu, Jun 29, 2017 at 2:03 PM, Mike Perez wrote: > > > > > >> Hello all, > > >> > > >> Wes has just took my ugly mock up of the contributor portal idea and > > >> came up with this [1]. > > >> > > >> Here’s what he said: > > >> > > >> "The idea is to help get potential contributors to the right place, > > >> using the outline Mike put together. Rather than sending people to a > > >> different page for each contribution type, users would be able to see > > >> what options are available all on this page. We’d send them to any > > >> necessary page(s) once they’ve gone through this quasi-wizard. Is this > > >> along the lines of what you were thinking? page 2 shows the view once > > >> you’ve clicked “Code” on page 1 (just in case that wasn’t super > > >> obvious) Thanks!” > > >> > > >> What do you all think? This does change things a bit of instead of the > > >> landing page being more obvious of a resource of links, it’s both for > > >> new and current contributors. Current contributors would hopefully be > > >> able to see the resource links below. > > >> > > >> Keep in mind that we will be working in the “Top 5 requested help” and > > >> as suggested by Clark, an option of “I don’t know where I want to > > >> start, but I want to help” kind of option. This would direct people to > > >> resources such as Upstream University, mentor program, low hanging > > >> fruit, that release priority idea I talked about earlier, etc. > > >> > > >> Personally I like it! > > >> > > >> > > >> [1] - https://www.dropbox.com/s/3q172qwfkik1ysd/contributor-port > > >> al.pdf?dl=0 > > >> > > >> — > > >> Mike Perez > > >> > > >> On June 27, 2017 at 13:48:36, Mike Perez (thin...@gmail.com) wrote: > > >> > Hello all, > > >> > > > >> > Every month we have people asking on IRC or the dev mailing list > having > > >> interest in working > > >> > on OpenStack, and sometimes they're given different answers from > > >> people, or worse, > > >> > no answer at all. > > >> > > > >> > Suggestion: lets work our efforts together to create some common > > >> documentation so that > > >> > all teams in OpenStack can benefit. > > >> > > > >> > First it’s important to note that we’re not just talking about code > > >> projects here. OpenStack > > >> > contributions come in many forms such as running meet ups, > identifying > > >> use cases (product > > >> > working group), documentation, testing, etc. We want to make sure > those > > >> potential contributors > > >> > feel welcomed too! > > >> > > > >> > What is common documentation? Things like setting up Git, the many > > >> accounts you need > > >> > to setup to contribute (ge
[Openstack-operators] OpenStack Operators Midcycle
Hey everyone, Happy 4th of July Eve! We have the upcoming Operator Midcycle in Mexico City, Mexico August 9-10th, 2017. Sign up via Eventbrite now*, space is limited* - https://www.eventbrite.com/e/mexico-city-openstack-operators-meetup-tickets-34989052197 We are taking session ideas and need your help generating them. Right now we have Kubernetes, Containers, NFV, and few more - https://etherpad.openstack.org/p/MEX-ops-meetup -- Kind regards OpenStack User Committee (Edgar, Jon, Melvin, Shamail, Shilla) ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] OpenStack Operators Midcycle
Just a friendly reminder for those who are waking up on the other side of the globe. Please take a moment to put some ideas for sessions in the etherpad - https://etherpad.openstack.org/p/MEX-ops-meetup Even if you are not able to make the midcycle, please take time to propose sessions. On Mon, Jul 3, 2017 at 7:40 AM, Melvin Hillsman wrote: > Hey everyone, > > Happy 4th of July Eve! We have the upcoming Operator Midcycle in Mexico > City, Mexico August 9-10th, 2017. Sign up via Eventbrite now*, space is > limited* - https://www.eventbrite.com/e/mexico-city-openstack- > operators-meetup-tickets-34989052197 > > We are taking session ideas and need your help generating them. Right now > we have Kubernetes, Containers, NFV, and few more - > https://etherpad.openstack.org/p/MEX-ops-meetup > > -- > Kind regards > > OpenStack User Committee > (Edgar, Jon, Melvin, Shamail, Shilla) > -- Kind regards, Melvin Hillsman mrhills...@gmail.com mobile: (832) 264-2646 Learner | Ideation | Belief | Responsibility | Command ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] UC WG/Team Requirements
Hey everyone, Please take time today to offer any additional comments/questions/concerns to the following document - https://docs.google.com/document/d/1r3KwaG-SbvaKCuAE52XwPCF7cRGDrNRg6dUhPQWs0vU This document establishes the requirements for current and future UC governed working groups and teams. We need to ensure we have this done before upcoming UC election so your feedback is greatly appreciated. -- Kind regards, OpenStack User Committee (Edgar, Jon, Melvin, Shamail, Shilla) ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
