Re: [Openstack] [openstack-dev] [nova][api] Novaclient redirect endpoint https into http

On 07/05/2018 01:55 PM, melanie witt wrote: +openstack-dev@ On Wed, 4 Jul 2018 14:50:26 +, Bogdan Katynski wrote: But, I can not use nova command, endpoint nova have been redirected from https to http. Here:http://prntscr.com/k2e8s6  (command: nova –insecure service list) First of all, it

[Openstack] All Hail our Newest Release Name - OpenStack Rocky

Hey everybody! There isn't a ton more to say past the subject. The "R" release of OpenStack shall henceforth be known as "Rocky". I believe it's the first time we've managed to name a release after a community member - so please everyone buy RockyG a drink if you see her in Boston. For tho

[Openstack] OpenStack "R" Release Naming Preliminary Results

Hello all! We left the voting open for an additional week because of how long it took to get emails sent out and the subsequent email issues. We'll be looking at options for next time to make that better. The raw results are below - however... **PLEASE REMEMBER** that these now have to go th

Re: [Openstack] Emails for OpenStack R Release Name voting going out - please be patient

On 04/06/2017 07:34 AM, Monty Taylor wrote: Hey all! I've started the R Release Name poll and currently am submitting everyone's email address to the system. In order to not make our fine friends at Carnegie Mellon (the folks who run the CIVS voting service) upset, I have a script th

[Openstack] Emails for OpenStack R Release Name voting going out - please be patient

Hey all! I've started the R Release Name poll and currently am submitting everyone's email address to the system. In order to not make our fine friends at Carnegie Mellon (the folks who run the CIVS voting service) upset, I have a script that submits the emails one at a time with a half-secon

[Openstack] Release Naming for R - it's that time again!

Hey everybody, It's your favorite time of the year - it's time for us to pick a name for our "R" release. Since the associated Summit will be in Vancouver, the Geographic Location has been chosen as "British Columbia". Nominations are now open. Please add suitable names to https://wiki.openstack

[Openstack] P and Q naming: all hail Pike and Queens

Hey everybody, As you all know, voting is only one step in the selection process. We also have to have vetting done on the choices to identify risk associated with the selected names. This time around, the top choice by vote for both P and Q was too problematic, so we moved down to the next most

[Openstack] Release Naming polls for P and Q ended, Legal Review under way

Hey everybody, I ended the polls for P and Q this morning. Because we had issues getting working poll links to everyone initially, I kept them open a bit longer than originally stated to make sure everyone had a chance to vote. I've submitted the results to the foundation staff who are now puttin

Re: [Openstack] Naming polls - and some issues

On 07/12/2016 04:40 AM, Monty Taylor wrote: > Hey all! > > The poll emails for the P and Q naming have started to go out - and > we're experiencing some difficulties. Not sure at the moment what's > going on ... but we'll keep working on the issues and get ballots t

Re: [Openstack] [openstack-dev] Naming polls - and some issues

Any time is a good time. On 07/17/2016 04:54 PM, Michael Still wrote: > So, is now a good time to mention that "Quamby" is the name of a local > prison? > > Michael > > > > On Fri, Jul 15, 2016 at 7:50 PM, Eoghan Glynn > wrote: > > > > > (top posting on purpos

Re: [Openstack] [openstack-dev] Naming polls - and some issues

(top posting on purpose) I have re-started the Q poll and am slowly adding all of you fine folks to it. Let's keep our fingers crossed that it works this time. I also removed Quay. Somehow my brain didn't process the "it would be like naming the S release "Street"" when reading the original names

Re: [Openstack] Naming polls - and some issues

On 07/12/2016 05:58 PM, Daniel P. Berrange wrote: > On Tue, Jul 12, 2016 at 05:40:07PM +0800, Monty Taylor wrote: >> Hey all! >> >> The poll emails for the P and Q naming have started to go out - and >> we're experiencing some difficulties. Not sure at the moment

[Openstack] Naming polls - and some issues

Hey all! The poll emails for the P and Q naming have started to go out - and we're experiencing some difficulties. Not sure at the moment what's going on ... but we'll keep working on the issues and get ballots to everyone as soon as we can. Sorry for any confusion. Monty __

[Openstack] Release naming for P and Q open for nominations

Hey everyone! It's time to pick a name for the P and Q releases. If you have a name you'd like us to vote on, please add it here: https://wiki.openstack.org/wiki/Release_Naming/P_Proposals https://wiki.openstack.org/wiki/Release_Naming/Q_Proposals The nominations will be open until 2016-06-28

[Openstack] All hail Newton and Ocata

If you couldn't tell from the subject line, we've gotten clearance from our friends on the Foundation staff and their legal team to be able to announce the names of the N and O cycles. The N release will be called "Newton" Newton was the overall winner of the Condorcet poll. While you might be

[Openstack] Naming Polls for N and O are open

Hey everybody! The naming polls for N and O have started. You should have received an email for each of them. They'll be open until the end of Dec 22 UTC. Once there are presumptive winners in each, please remember that we will then have the names vetted by the OpenStack Foundation's lawyers,

[Openstack] Nominations open for the N and O names of OpenStack

Hey everybody! It's release naming time, and this time we get to do two at once! If you'd like to propose a name, there are two wiki pages: For the N release, where the geographic region is "Texas Hill Country": https://wiki.openstack.org/wiki/Release_Naming/N_Proposals For the O release, whe

[Openstack] OpenStack Mitaka (三鷹) - Our next release name has been selected

Hi everybody! Ok. There is nothing more actually useful I can say that isn't in the subject line. As I mentioned previously, the preliminary results from our name election are here: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc As you are all probably aware by now, as a fol

[Openstack] Rescinding the M name decision

Hi everyone! In light of issues raised concerning the initially selected name for the M release (Meiji), that name will not be used. It turns out fully open community and fully inclusive collaboration is a hard thing to get right. On the one hand, we do not want to exclude anyone's input or contr

Re: [Openstack] [openstack-community] [openstack-dev] OpenStack Meiji (明治) - Our next release name has been selected

ion 13. We already use semver. This is not a realistic solution to anything. > > Cheers > > Tristan > > > > > > *From:* Jaesuk Ahn [mailto:bluejay@gmail.com] > *Sent:* Wednesday, 8 July 2015 2:41 PM > *To:* OpenStack Development Mailing List; Openstack Us

[Openstack] OpenStack Meiji (明治) - Our next release name has been selected

Hi everybody! Ok. There is nothing more actually useful I can say that isn't in the subject line. As I mentioned previously, the preliminary results from our name election are here: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4983776e190c8dbc As a follow on step, the OpenStack Foundation

[Openstack] M Naming Poll ended - results still need to clear legal

Hey all! The M naming poll has concluded. I'd say "and the winner is ..." except we still need to get the winning choice(s) vetted for legal entanglements. Feel free to go and look at the results, they are publicly available - but please DON'T start making t-shirts or having parties (ok, have as

[Openstack] Starting the M Release Name Poll

Hey everybody! I've started the poll for the M release. By now, you should have gotten an email with a link to the vote. If you did not and think that you should have, please let me know (directly, not to the mailing list please) and I can re-send and/or fix as necessary. Please remember that the

[Openstack] Release naming for M open for nominations

Hey everyone! It's time to pick a name for the M release. If you have a name you'd like us to vote on, please add it here: https://wiki.openstack.org/wiki/Release_Naming/M_Proposals The nominations will be open until 2015-06-07 23:59:59 UTC. If you don't remember the rules, they're here: http

Re: [Openstack] [Foundation Board] Resolutions from the Technical Committee

I believe the part of the thing Jonathan was referencing that the TC is talking about is the final line of 4.1(b): "The Secretary shall maintain a list of the modules in the Core OpenStack Project which shall be posted on the Foundation’s website." Which led us to believe that we needed to sugges

Re: [Openstack] [Foundation Board] Resolutions from the Technical Committee

g some relevant facts. > Thanks Mark! I believe you said what I was trying to communicate in a much clearer and less confrontational manner. Can you just talk for me? > > On Nov 14, 2013 7:29 AM, Monty Taylor wrote: >> >> >> >> On 11/14/2013 03:24 AM, Thierry Ca

Re: [Openstack] [Foundation Board] Resolutions from the Technical Committee

On 11/14/2013 03:24 AM, Thierry Carrez wrote: > Joshua McKenty wrote: >> Thierry, I'll make sure this motion lands on the agenda for discussion >> at the next board meeting. I don't see a gerritt entry for that motion, >> though - where is the vote recorded? > > The review is at: > https://revie