[Openstack] [all] All Hail our Newest Release Name - OpenStack Train
Hi everybody! As the subject reads, the "T" release of OpenStack is officially "Train". Unlike recent choices Train was the popular choice so congrats! Thanks to everybody who participated and help with the naming process. Lets make OpenStack Train the release so awesome that people can't help but choo-choo-choose to run it[1]! Yours Tony. [1] Too soon? Too much? signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] [all] Results of the T release naming poll. open
Hello all! The results of the naming poll are in! **PLEASE REMEMBER** that these now have to go through legal vetting. So it is too soon to say 'OpenStack Train' is our next release, given that previous polls have had some issues with the top choice. In any case, the names will be sent off to legal for vetting. As soon as we have a final winner, I'll let you all know. https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_aac97f1cbb6c61df&rkey=7c8b5588574494c1 Result 1. Train (Condorcet winner: wins contests with all other choices) 2. Tiger loses to Train by 142–70 3. Timber loses to Train by 142–72, loses to Tiger by 100–76 4. Trail loses to Train by 150–55, loses to Timber by 93–62 5. Telluride loses to Train by 155–56, loses to Trail by 81–69 6. Teller loses to Train by 158–46, loses to Telluride by 70–67 7. Treasure loses to Train by 151–52, loses to Teller by 68–67 8. Teakettle loses to Train by 158–49, loses to Treasure by 75–67 9. Tincup loses to Train by 157–47, loses to Teakettle by 67–60 10. Turret loses to Train by 158–48, loses to Tincup by 75–56 11. Thomas loses to Train by 159–42, loses to Turret by 66–63 12. Trinidad loses to Train by 153–44, loses to Thomas by 70–56 13. Troublesome loses to Train by 165–41, loses to Trinidad by 69–62 14. Thornton loses to Train by 163–35, loses to Troublesome by 62–59 15. Tyrone loses to Train by 163–35, loses to Thornton by 58–38 16. Tarryall loses to Train by 170–31, loses to Tyrone by 54–50 17. Timnath loses to Train by 170–23, loses to Tarryall by 60–32 18. Tiny Town loses to Train by 168–29, loses to Timnath by 45–43 19. Torreys loses to Train by 167–29, loses to Tiny Town by 48–40 20. Trussville loses to Train by 169–25, loses to Torreys by 43–34 signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack-dev] [all]Naming the T release of OpenStack -- Poll open
Hi all, Time is running out for you to have your say in the T release name poll. We have just under 3 days left. If you haven't voted please do! On Tue, Oct 30, 2018 at 04:40:25PM +1100, Tony Breeds wrote: > Hi folks, > > It is time again to cast your vote for the naming of the T Release. > As with last time we'll use a public polling option over per user private URLs > for voting. This means, everybody should proceed to use the following URL to > cast their vote: > > > https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e > > We've selected a public poll to ensure that the whole community, not just > gerrit > change owners get a vote. Also the size of our community has grown such that > we > can overwhelm CIVS if using private urls. A public can mean that users > behind NAT, proxy servers or firewalls may receive an message saying > that your vote has already been lodged, if this happens please try > another IP. > > Because this is a public poll, results will currently be only viewable by > myself > until the poll closes. Once closed, I'll post the URL making the results > viewable to everybody. This was done to avoid everybody seeing the results > while > the public poll is running. > > The poll will officially end on 2018-11-08 00:00:00+00:00[1], and results > will be > posted shortly after. > > [1] https://governance.openstack.org/tc/reference/release-naming.html > --- > > According to the Release Naming Process, this poll is to determine the > community preferences for the name of the T release of OpenStack. It is > possible that the top choice is not viable for legal reasons, so the second or > later community preference could wind up being the name. > > Release Name Criteria > - > > Each release name must start with the letter of the ISO basic Latin alphabet > following the initial letter of the previous release, starting with the > initial release of "Austin". After "Z", the next name should start with > "A" again. > > The name must be composed only of the 26 characters of the ISO basic Latin > alphabet. Names which can be transliterated into this character set are also > acceptable. > > The name must refer to the physical or human geography of the region > encompassing the location of the OpenStack design summit for the > corresponding release. The exact boundaries of the geographic region under > consideration must be declared before the opening of nominations, as part of > the initiation of the selection process. > > The name must be a single word with a maximum of 10 characters. Words that > describe the feature should not be included, so "Foo City" or "Foo Peak" > would both be eligible as "Foo". > > Names which do not meet these criteria but otherwise sound really cool > should be added to a separate section of the wiki page and the TC may make > an exception for one or more of them to be considered in the Condorcet poll. > The naming official is responsible for presenting the list of exceptional > names for consideration to the TC before the poll opens. > > Exact Geographic Region > --- > > The Geographic Region from where names for the S release will come is Colorado > > Proposed Names > -- > > * Tarryall > * Teakettle > * Teller > * Telluride > * Thomas : the Tank Engine > * Thornton > * Tiger > * Tincup > * Timnath > * Timber > * Tiny Town > * Torreys > * Trail > * Trinidad > * Treasure > * Troublesome > * Trussville > * Turret > * Tyrone > > Proposed Names that do not meet the criteria (accepted by the TC) > - > > * Train🚂 : Many Attendees of the first Denver PTG have a story to tell about > the trains near the PTG hotel. We could celebrate those stories with this > name > > Yours Tony. > __ > 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 Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack-dev] [all]Naming the T release of OpenStack -- Poll open
On Tue, Oct 30, 2018 at 11:25:02AM -0700, iain macdonnell wrote: > I must be losing it. On what planet is "Tiny Town" a single word, and > "Troublesome" not more than 10 characters? Sorry for the mistake. Should either of these names win the popular vote clearly they would not be viable. Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] [all]Naming the T release of OpenStack -- Poll open
Hi folks, It is time again to cast your vote for the naming of the T Release. As with last time we'll use a public polling option over per user private URLs for voting. This means, everybody should proceed to use the following URL to cast their vote: https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_aac97f1cbb6c61df&akey=b9e448b340787f0e We've selected a public poll to ensure that the whole community, not just gerrit change owners get a vote. Also the size of our community has grown such that we can overwhelm CIVS if using private urls. A public can mean that users behind NAT, proxy servers or firewalls may receive an message saying that your vote has already been lodged, if this happens please try another IP. Because this is a public poll, results will currently be only viewable by myself until the poll closes. Once closed, I'll post the URL making the results viewable to everybody. This was done to avoid everybody seeing the results while the public poll is running. The poll will officially end on 2018-11-08 00:00:00+00:00[1], and results will be posted shortly after. [1] https://governance.openstack.org/tc/reference/release-naming.html --- According to the Release Naming Process, this poll is to determine the community preferences for the name of the T release of OpenStack. It is possible that the top choice is not viable for legal reasons, so the second or later community preference could wind up being the name. Release Name Criteria - Each release name must start with the letter of the ISO basic Latin alphabet following the initial letter of the previous release, starting with the initial release of "Austin". After "Z", the next name should start with "A" again. The name must be composed only of the 26 characters of the ISO basic Latin alphabet. Names which can be transliterated into this character set are also acceptable. The name must refer to the physical or human geography of the region encompassing the location of the OpenStack design summit for the corresponding release. The exact boundaries of the geographic region under consideration must be declared before the opening of nominations, as part of the initiation of the selection process. The name must be a single word with a maximum of 10 characters. Words that describe the feature should not be included, so "Foo City" or "Foo Peak" would both be eligible as "Foo". Names which do not meet these criteria but otherwise sound really cool should be added to a separate section of the wiki page and the TC may make an exception for one or more of them to be considered in the Condorcet poll. The naming official is responsible for presenting the list of exceptional names for consideration to the TC before the poll opens. Exact Geographic Region --- The Geographic Region from where names for the S release will come is Colorado Proposed Names -- * Tarryall * Teakettle * Teller * Telluride * Thomas : the Tank Engine * Thornton * Tiger * Tincup * Timnath * Timber * Tiny Town * Torreys * Trail * Trinidad * Treasure * Troublesome * Trussville * Turret * Tyrone Proposed Names that do not meet the criteria (accepted by the TC) - * Train🚂 : Many Attendees of the first Denver PTG have a story to tell about the trains near the PTG hotel. We could celebrate those stories with this name Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [Openstack-sigs] [all] Bringing the community together (combine the lists!)
On Thu, Aug 30, 2018 at 09:12:57PM +, Jeremy Stanley wrote: > On 2018-08-31 01:13:58 +0800 (+0800), Rico Lin wrote: > [...] > > What needs to be done for this is full topic categories support > > under `options` page so people get to filter emails properly. > [...] > > Unfortunately, topic filtering is one of the MM2 features the > Mailman community decided nobody used (or at least not enough to > warrant preserving it in MM3). I do think we need to be consistent > about tagging subjects to make client-side filtering more effective > for people who want that, but if we _do_ want to be able to upgrade > we shouldn't continue to rely on server-side filtering support in > Mailman unless we can somehow work with them to help in > reimplementing it. The suggestion is to implement it as a 3rd party plugin or work with the mm community to implement: https://wiki.mailman.psf.io/DEV/Dynamic%20Sublists So if we decide we really want that in mm3 we have options. Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] diskimage-builder: prepare ubuntu 17.x images
On Thu, Feb 08, 2018 at 10:53:14PM +0200, Volodymyr Litovka wrote: > Hi colleagues, > > does anybody here know how to prepare Ubuntu Artful (17.10) image using > diskimage-builder? > > diskimage-builder use the following naming style for download - > $DIB_RELEASE-server-cloudimg-$ARCH-root.tar.gz > > and while "-root" names are there for trusty/amd64 and xenial/amd64 distros, > these archives for artful (and bionic) are absent on > cloud-images.ubuntu.com. There are just different kinds of images, not > source tree as in -root archives. > > I will appreciate any ideas or knowledge how to customize 17.10-based image > using diskimage-builder or in diskimage-builder-like fashion. You might like to investigate the ubuntu-minimal DIB element which will build your ubuntu image from apt rather than starting with the pre-built image. In the meantime I'll look at how we can consume the .img file, which is similar to what we'd need to do for Fedora Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] tripleO Error No valid host was found
On Wed, Jan 31, 2018 at 06:10:11PM -0500, Satish Patel wrote: > I am playing with tripleO and getting following error when deploying > overcloud, I doing all this on VMware Workstation with fake_pxe > driver, I did enable drive in ironic too. > > What could be wrong here? There's lots that could be wrong sadly. Testign under VMware is minimal to none. There are some good tips at: https://docs.openstack.org/tripleo-docs/latest/install/troubleshooting/troubleshooting.html Specifically: https://docs.openstack.org/tripleo-docs/latest/install/troubleshooting/troubleshooting-overcloud.html#no-valid-host-found-error Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [Devstack]Installation of Barbican failing in ubuntu 16.04 LTS
On Wed, Jan 31, 2018 at 09:21:34AM +0530, Himanshu Gupta wrote: > Hi Guys, > > I was trying to install the Devstack(Ocata branch) on the ubuntu 16.04 LTS > by performing pre-requisite steps and running stack.sh. But the > installation throws an error while installing Barbican. It throws the > following exception: The bottom line is that the uwsgi code isn't available in the ocata branch of devstack So you either need to backport I1d89be1f1b36f26eaf543b99bde6fdc5701474fe to ocata (which probably isn't appropriate at this stage) or have barbican in ocata run stand alone. Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Devstack branch not found
On Tue, Jul 25, 2017 at 10:22:18AM +0200, Silvia Fichera wrote: > Hi all, > I need to use Openstack Mitaka, I usually install it by devstack. When I > cloned from git I have this error: > > git clone -b stable/mitaka https://git.openstack.org/openstack-dev/devstack > Cloning into 'devstack'... > fatal: Remote branch stable/mitaka not found in upstream origin > > Where can I find the branch I need? That's right stable/mitaka has been marked End Of Life (EOL) if you *really* need it you can do git clone https://git.openstack.org/openstack-dev/devstack git checkout -b stable/mitaka mitaka-eol This will get you the code as it was retired. Be warned that most of the other service projects have also been retired so when devstack attempts to checkout the stable/mitaka branch of (say keystone) you'll have the same issue. It's strongly advised you move up to newton or better yet ocata or master :) Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Stable/ocata patches
On Sun, Feb 05, 2017 at 05:18:21PM +, Gary Kotton wrote: > Hi, > Are we blocking patches for stable Ocata? It is really unclear why [i] is > blocked. My understanding is that bugs can be backported? This was hit under > load testing and caused neutron to break. During this stabilisation phase we only backport release critical bugs. Which is at the discretion of the $project (Neutron) drivers team. Once Ocata is released then normal backports can resume. Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Upgrade Mitaka to Newton. Nova 13 does not work with Nova 14
On Wed, Dec 14, 2016 at 10:36:37AM +0300, Evgeniy Ivanov wrote: > Hello! > > I'm experiencing some kind of a bug, when I have a controller with mitaka > and a controller with Newton. > When I upgraded the first part of my cluster to Newton, the second part > stopped to work (nova-api). > > I got this error: > oslo_service.service ServiceTooOld: This service is older (v9) than the > minimum (v15) version of the rest of the deployment. Unable to continue. > > So, as we can see, all those dialogs, manuals, docs, posts which are talking > about compatibility between 2 releases are wrong, aren't they? > > I will be happy to read some thoughts from you guys, thanks! > > How to reproduce: > Install nova 13 on 2 nodes > Disable the first node > Upgrade the first node to nova 14 > Restart nova-api on the second node (13 ver.) At what point of http://docs.openstack.org/developer/nova/upgrade.html did you hit the problem? That will help us narrow down the search for you problem. Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] i want to kilo verion /var/www/cgi-bin/keystone/admin
On Fri, Sep 09, 2016 at 05:03:35PM +0800, YOUDI wrote: > I am a new user openstack > I want install kilo version openstack Kilo has been End-of-Lifed (EOLd). I suggest you start with mitaka (as liberty will be EOLd soonish) If you *really* need kilo you'll need to proide a little more information on your requirements and what you've tried. Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [neutron][devstack]subnet created with wrong gateway
On Sun, Aug 21, 2016 at 05:28:44PM +0530, Akilesh K wrote: > Hi, > I am using devstack for the first time and I see that it has created a > subnet like below. The cidr and gateway do not match. Because of this > devstack fails to run completely and fails while attaching a router to this > subnet. Why is devstack doing this?? You also need to specify NETWORK_GATEWAY in your local.conf: NETWORK_GATEWAY=10.4.128.1 should match: FIXED_RANGE=10.4.128.0/20 Our docs need updating as we recently switched from nova to neutron as the default network provider. Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack] devstack kilo setup
On Thu, Jun 30, 2016 at 02:16:55AM +0200, Ahmed Medhat wrote: > Regarding git describe, it shows that : > kilo-2-1146-g8834ac4 Interesting I can't find that SHA in my clone. > while git branch shows: > stable/liberty Okay that's fine. > So what is that mix ? :) Nothing to worry about. Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack] devstack kilo setup
On Thu, Jun 30, 2016 at 02:08:35AM +0200, Ahmed Medhat wrote: > Openbaton.com Okay based on thise tweet I think mitaka is fine. https://twitter.com/OpenBaton/status/741304586674274304 Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack] devstack kilo setup
On Thu, Jun 30, 2016 at 02:08:04AM +0200, Ahmed Medhat wrote: > Not fo other purpose , it was devstack kilo. And now I need devstack > liberty. Oh in that case you're probably okay with just running unstack.sh and clean.sh. Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack] devstack kilo setup
On Thu, Jun 30, 2016 at 12:16:58AM +0200, Ahmed Medhat wrote: > Thanks for your reply. > > I tried to install liberty but I got this error during stacking. > > could not find user admin (http 401) Please provide some of the log (probably in /opt/stack/log/stack.sh.log or similar) Also can you run git describe in your devstack tree? Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack] devstack kilo setup
On Thu, Jun 30, 2016 at 01:37:09AM +0200, Ahmed Medhat wrote: > I know clean.sh :) i mean what else should I do ? > > I am installing it directly on machine no VMs. Ah :( After you've run clean you can remove the whole /opt/stack directory Also look at /usr/local for tools and python packages that are "probaby" from OpenStack. Cleaning up a machine that you use for other purposes is tough, and running devstack (well any stack really) is best done on a dedicated machine / VM Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack] devstack kilo setup
On Thu, Jun 30, 2016 at 12:35:49AM +0200, Ahmed Medhat wrote: > Thanks Tony for reply. > > I ill use liberty , i can not use master because I am using Orchestrator > and I am not sure if it works with Mitaka or Master or not. Can you provide a link to this "Orchestrator" ? Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack] devstack kilo setup
On Wed, Jun 29, 2016 at 03:09:52PM +0200, Ahmed Medhat wrote: > Hi all, > > I am installing devstack kilo. > > while stacking, found that error : error: pathspec 'stable/kilo' did not > match any file(s) known to git. Kilo is no longer available it began it's path to EOL in May. You can use liberty but if you'd starting a fresh devstack why not master? Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [all][stable] OpenStack 2015.1.4 released (EOL release)
On Tue, May 10, 2016 at 11:30:30PM +0100, Dave Walker wrote: > Hi, > > The OpenStack Stable Maintenance team is happy to announce the release > of the 2015.1.4 stable Kilo release. We have been busy reviewing and > accepting backported bugfixes to the stable/kilo branches according > to the criteria set at: > https://wiki.openstack.org/wiki/StableBranch Thanks so much for doing this Dave! Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] some error of install-openstack-from-source
On Tue, Mar 08, 2016 at 10:41:49AM +0800, yewgang wrote: > Hi, > > I'm porting openstack from source into my environment, follows > https://developer.rackspace.com/blog/install-openstack-from-source/ > > I found the script in "Create the various users and directories needed for > the OpenStack services." has some error as follow: > > 1. miss "done" at the end of this script. > 2. we have to run this script using "bash", not "sh". Thanks for the report. That's a rackspace blog and not something in the control of the OpenStack community. Fortunately we happen to overlap somewhat. I've CC'd Lana who has access to those systems and *may* be able to make corrections. Yours Tony. signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [Devstack] Enabling n-net by default
On Sat, Feb 06, 2016 at 10:11:41AM +0900, Shinobu Kinjo wrote: > Hello, > > Does anyone know what the situation where "n-net" is required to use is? > My question comes from that that service still needs to be disabled > explicitly in local.conf and I've never used that. I'm not certain what you're asking. Do you: a) Want n-net ; or b) Want neutron c) something else? The devstack docs[1] are pretty good Yours Tony. [1] http://docs.openstack.org/developer/devstack/configuration.html signature.asc Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] [openstack-dev] Error Installing KILO release on powerpc
On Thu, Oct 08, 2015 at 11:08:06PM +0530, Rahul Arora wrote: > Hi Team > > I am trying to run Openstack KILO release on my powerpc platform.I am able > to cross compile all the KILO related packages using yocto framework.But > while running the following command i am getting below error messages. Wait what? cross compile? You'll need to explain more about your platform / setup as that really shoudlne't be needed. Are you installign from git, disto packages or something else? Havign said all that powerpc support is somewhat spotty. It certainly works but the build/setup experience will be a little more painful than normal. > keystone-manage db_sync > > Traceback (most recent call last): > File "/usr/bin/keystone-manage", line 30, in > from keystone import cli > File "/usr/lib/python2.7/site-packages/keystone/cli.py", line 27, in > > from keystone.common import sql > File "/usr/lib/python2.7/site-packages/keystone/common/sql/__init__.py", > line 15, in > from keystone.common.sql.core import * # noqa > File "/usr/lib/python2.7/site-packages/keystone/common/sql/core.py", line > 28, in > from oslo_db.sqlalchemy import session as db_session > File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/session.py", > line 300, in > from oslo_db.sqlalchemy import utils > File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/utils.py", line > 36, in > from sqlalchemy import inspect > ImportError: cannot import name inspect Seems like you just missed a dependancy. Yours Tony. pgpno2bYvPD1A.pgp Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Re: [Openstack] Need help to remove devstack and all related files completely
On Wed, Nov 26, 2014 at 07:17:38AM +, Hanan Liaqat wrote: > How to completely delete the devstack files so that i can clone devstack and > renew the devstaxck installation free of previous misconfigurations If you want a completely fresh install of everything. 1) reboot the system 2) clone devstack again into a new directory 3) setup your local.conf as you need 4) Add RECLONE to your local.conf: http://docs.openstack.org/developer/devstack/configuration.html#a-clean-install-every-time 5) run stack.sh That will give you a fresh install. Yours Tony. pgphZoobQO6YW.pgp Description: PGP signature ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
