Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

No, Magnum still uses Barbican as an optional dependency, and I believe nobody has proposed to remove Barbican entirely. I have no position about big tent but using Magnum as an example of "projects are not working together" is inappropriate. Best regards, Hongbin > -Original Message-

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-14 10:38 GMT+08:00 Cheng, Yingxin : > > On 7/14/16, 05:42, "Ed Leafe" wrote: > On Jul 12, 2016, at 2:43 AM, Cheng, Yingxin > wrote: > > 4. Capabilities are managed/grouped/abstracted by namespaces, and > scheduler

Re: [openstack-dev] [ironic] [oslo] Stevedore 1.16 breaks IPA gate

I assume this is connected into: https://review.openstack.org/#/c/334014/ Which was proposed a few weeks ago, I'd be nice to identify the causing review and see if we can find the authors to learn about why, If its needed, proposing a requirements block is fine with me (until we can get to

[openstack-dev] [Congress] Mascot

Hi all, As a reminder, we need to come up with a list of 2-3 mascots so the OpenStack Foundation can choose 1 and turn it into a logo for Congress. The mascots must come from the natural world (animals, plants, mountains, waterfalls, etc.). Deadline is July 27. I'll get the thread started with

Re: [openstack-dev] [DIB] [Ironic] [TripleO] Moving IPA element out of DIB tree

One more note I missed in the previous email. On Jul 15, 2016, at 1:46 PM, Ben Nemec > wrote: I think this probably makes sense, but some more thoughts inline. On 07/15/2016 03:13 PM, Stephane Miller wrote: To better support

[openstack-dev] [ironic] [oslo] Stevedore 1.16 breaks IPA gate

Hi all, I wanted to get a little more light on this bug discovered: https://bugs.launchpad.net/stevedore/+bug/1603542. Jim posted a summary of it today in #openstack-oslo and didn't get a response, and it's currently breaking IPA's gate. If someone familiar with stevedore could please triage

Re: [openstack-dev] [DIB] [Ironic] [TripleO] Moving IPA element out of DIB tree

A few notes inline; I'm not the best technical contact for IPA+DIB integration, but going to add a little bit of context here so you all can well-understand our goals. On Jul 15, 2016, at 4:28 PM, Gregory Haynes > wrote: On Fri, Jul 15, 2016, at

Re: [openstack-dev] [DIB] [TripleO] Should we have a DIB meeting?

On Fri, Jul 15, 2016, at 06:20 PM, Stephane Miller wrote: > There are a lot of interesting and complex changes going on with DIB > at the moment. This is a good thing, but it also means that we have > more complex decisions to make for the project. We've already taken > one step to address this in

Re: [openstack-dev] [Horizon] Angular action services and initScope

If we find that there is still a need to send the scope in that can’t be reasonably worked around, then the action services could be changed to be a factory. The injected action factory should have a factory function called by the controller which creates an instance of the action in each

Re: [openstack-dev] [DIB] [Ironic] [TripleO] Moving IPA element out of DIB tree

On Fri, Jul 15, 2016, at 03:46 PM, Ben Nemec wrote: > I think this probably makes sense, but some more thoughts inline. > > On 07/15/2016 03:13 PM, Stephane Miller wrote: > > To better support diskimage-builder based IPA images going forward, we'd > > like to move the ironic-agent element into

[openstack-dev] [DIB] [TripleO] Should we have a DIB meeting?

There are a lot of interesting and complex changes going on with DIB at the moment. This is a good thing, but it also means that we have more complex decisions to make for the project. We've already taken one step to address this in proposing a specs process

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Hi all, I agree with Vitaly that Sahara's actually tried very hard to be a good OpenStack citizen in re: integration with other Big Tent components (Heat, Barbican, Manila, Designate...) Frequently Saharans have decided to write such integrations in large part because it's the right thing to do

[openstack-dev] [api] testing openstackdocstheme and os-api-ref for API reference info

Hi -dev and -doc lists, and awesome devs Karen and Graham specifically - I want to figure out the best way to coordinate a release of both the theme and the sphinx extension so that we can test and publish and iterate on the new API reference information display and navigation. I think these

Re: [openstack-dev] How to develop a new [Cinder] driver?

On Jul 15, 2016, at 9:33 PM, Turbo Fredriksson wrote: > Is there a simpler way to do this? A followup question on that: I'm using a remote SAN and I've gotten the creation/deletion/iSCSI share/unshare on that to work just fine. However, when creating a volume from an image, the driver fails on

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Hello, "Less project communication" and "projects not working together because of fear of adding dependencies" is not so true, I think. In my opinion, Big Tent projects are always open for integrating with each other, and we are doing great job for making integration points much stronger. Since

Re: [openstack-dev] [DIB] [Ironic] [TripleO] Moving IPA element out of DIB tree

I think this probably makes sense, but some more thoughts inline. On 07/15/2016 03:13 PM, Stephane Miller wrote: > To better support diskimage-builder based IPA images going forward, we'd > like to move the ironic-agent element into the ironic-python-agent > repository. This will involve: > > -

[openstack-dev] How to develop a new [Cinder] driver?

I'm trying to port the/a Openstack-ZFS driver to Mitaka, but every time I do a change, I have to restart cinder-volume, run my test command, look through the log file, modify the driver, and back to beginning Is there a simpler way to do this? I'm not extremely fluent in Python (it's been over

[openstack-dev] [Horizon] Angular action services and initScope

Hi folks, Something that's been bothering me for a while is that the action services break the encapsulation model of Angular Services - that they are singletons, and consumable by multiple simultaneous consumers without those consumers affecting each other through their use of the Service. At

Re: [openstack-dev] [openstack-ansible] Project Mascot

What about a forest full of . The trees in the forest can be all the configuration options you can specify in OSA? ;)  -Original Message- From: Steve Lewis Reply: OpenStack Development Mailing List (not for usage questions) Date: 

[openstack-dev] [DIB] [Ironic] [TripleO] Moving IPA element out of DIB tree

To better support diskimage-builder based IPA images going forward, we'd like to move the ironic-agent element into the ironic-python-agent repository. This will involve: - Improving support for having multiple copies of an element, so that we may deprecate the diskimage-builder repository copy

Re: [openstack-dev] [openstack-ansible] Project Mascot

I am happy to support the Cape Buffalo mascot. On Fri, Jul 15, 2016 at 8:03 AM, Truman, Travis wrote: > I like the bull, cape buffalo and oxen ideas. Any would work well for us. > > From: Matt Thompson > Reply-To: "OpenStack Development

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Some specific things: Magnum trying to not use Barbican as it adds an addition dependency. See the discussion on the devel mailing list for details. Horizon discussions at the summit around wanting to use Zaqar for dynamic ui updates instead of polling, but couldn't depend on a non widely

Re: [openstack-dev] [neutron] Keystone V3 alignment: renaming tenant_id columns to project_id

> On Jul 15, 2016, at 11:33 AM, Neil Jerram wrote: > > I've put my name against networking-calico, but I believe it's a no-op for me > at this stage of the tenant->project transition. The occurrences of 'tenant' > in networking-calico's code are: > >

Re: [openstack-dev] [tc][all] Plugins for all

On 15/07/2016 18:24, Luigi Toscano wrote: > On Friday, 15 July 2016 17:05:41 CEST Hayes, Graham wrote: >> On 15/07/2016 17:52, Luigi Toscano wrote: >>> On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: On 15/07/2016 17:10, Andrew Laski wrote: >> Tempest plugins are another

Re: [openstack-dev] [tc][all] Plugins for all

On Friday, 15 July 2016 17:05:41 CEST Hayes, Graham wrote: > On 15/07/2016 17:52, Luigi Toscano wrote: > > On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: > >> On 15/07/2016 17:10, Andrew Laski wrote: > Tempest plugins are another example. Approximately 30 of the 36 > current

Re: [openstack-dev] [tc][all] Plugins for all

On 15/07/2016 17:52, Luigi Toscano wrote: > On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: >> On 15/07/2016 17:10, Andrew Laski wrote: > Tempest plugins are another example. Approximately 30 of the 36 current plugins are using resources that are not supposed to be used,

Re: [openstack-dev] [tc][all] Plugins for all

On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: > On 15/07/2016 17:10, Andrew Laski wrote: > >> Tempest plugins are another example. Approximately 30 of the 36 > >> current plugins are using resources that are not supposed to be > >> used, and are an unstable interface. Projects in

Re: [openstack-dev] [tc][all] Plugins for all

On 15/07/2016 17:10, Andrew Laski wrote: > > > On Thu, Jul 14, 2016, at 03:21 PM, Hayes, Graham wrote: >> I just proposed a review to openstack/governance repo [0] that aims >> to have everything across OpenStack be plugin based for all cross >> project interaction, or allow all projects access to

Re: [openstack-dev] [neutron] Keystone V3 alignment: renaming tenant_id columns to project_id

I've put my name against networking-calico, but I believe it's a no-op for me at this stage of the tenant->project transition. The occurrences of 'tenant' in networking-calico's code are: ./networking_calico/plugins/calico/plugin.py:45:LOG.info("Forcing ML2 tenant_network_types to

Re: [openstack-dev] [kolla] our mascot - input needed

On Fri, Jul 15, 2016 at 1:38 AM, Steven Dake (stdake) wrote: > Hey folks, > > The OpenStack foundation is putting together mascots for every project with > a proper artist doing the work. The cool thing about this is we a) get > stickers b) have consistent look and feel among

Re: [openstack-dev] Python 35 jobs currently broken (was Re: New Python35 Jobs coming)

On Fri, Jul 15, 2016, at 08:05 AM, Julien Danjou wrote: > On Wed, Jul 06 2016, Andreas Jaeger wrote: > > > New images for Xenial have been build and have been uploaded, first > > tests are passing. You should now be able to check python35 jobs for > > anything that's starting now. > > Do we need

Re: [openstack-dev] [tc][all] Plugins for all

On Thu, Jul 14, 2016, at 03:21 PM, Hayes, Graham wrote: > I just proposed a review to openstack/governance repo [0] that aims > to have everything across OpenStack be plugin based for all cross > project interaction, or allow all projects access to the same internal > APIs and I wanted to give a

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On 14/07/2016 21:33, Fox, Kevin M wrote: > I'm going to go ahead and ask the difficult question now as the answer is > relevant to the attached proposal... > > Should we reconsider whether the big tent is the right approach going forward? > > There have been some major downsides I think to the

Re: [openstack-dev] [tc][all] Plugins for all

On 14/07/2016 21:20, Matt Riedemann wrote: > On 7/14/2016 2:21 PM, Hayes, Graham wrote: >> I just proposed a review to openstack/governance repo [0] that aims >> to have everything across OpenStack be plugin based for all cross >> project interaction, or allow all projects access to the same

[openstack-dev] [tripleo] service validation during deployment steps

Hi, Some people on the field brought interesting feedback: "As a TripleO User, I would like the deployment to stop immediately after an resource creation failure during a step of the deployment and be able to easily understand what service or resource failed to be installed". Example: If during

Re: [openstack-dev] [nova][scheduler] A simple solution for better scheduler performance

Hi John, Thanks for the reply. There’re two rounds of experiments: Experiment A [3] is deployed by devstack. There’re 1000 compute services with fake virt driver. The DB driver is the devstack default PyMySQL. And the scheduler driver is the default filter scheduler. Experiment B [4] is the

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Kevin, can you please be *specific* about your complaints below? Saying things like "less project communication" and "projects not working together because of fear of adding dependencies" and "worse user experience" are your personal opinions. Please back those opinions up with specific

Re: [openstack-dev] Mascot/logo for your project

On Mon, Jul 11 2016, Heidi Joy Tretheway wrote: > The Foundation would like to help promote OpenStack projects in the big tent > with branding and marketing services. The idea is to create a family of logos > for OpenStack projects that are unique, yet immediately identifiable as part > of >

[openstack-dev] [nova] notification subteam meeting rescheduled to biweekly

Hi, As agreed on the last notification subteam meeting [1] I proposed to reschedule the subteam meeting to biweekly [2] as the workload is decreased due to non priority feature freeze. So the next notification subteam meeting will be held on 2016.07.26 17:00 UTC [1] on #openstack-meeting-4.

Re: [openstack-dev] [openstack-ansible] Project Mascot

I like the bull, cape buffalo and oxen ideas. Any would work well for us. From: Matt Thompson > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] Python 35 jobs currently broken (was Re: New Python35 Jobs coming)

On Wed, Jul 06 2016, Andreas Jaeger wrote: > New images for Xenial have been build and have been uploaded, first > tests are passing. You should now be able to check python35 jobs for > anything that's starting now. Do we need to do anything to move the job to voting, or will this happen

Re: [openstack-dev] [release][documentation][telemetry][murano][trove] missing milestones

We’re in the process of tearing down murano apps into separate production grade apps and murano-examples, that are only good as, well examples. So we do not intend to include murano-apps as a deliverable in this cycle. (Would probably need to update the release model for it as soon as possible

[openstack-dev] [nova][scheduler] Capability Modeling - Newton Mid-cycle Status

The current focus of improving the Nova Scheduler is progressing, with ResourceProviders now representing the quantities of the different resources available for virtualization. But these resources also have varying qualities that are not consumed by a VM, but describe something about the

[openstack-dev] [release] Release countdown for week R-11, July 18-22

Focus - Major feature work should be well under way as we pass the second milestone. General Notes - Keep in mind that we freeze releases of all libraries between the third milestone and the final release to give downstream packagers time to vet the libraries. Only emergency bug

[openstack-dev] [monasca] Announcing Monasca Analytics

Dear all, I have the pleasure to introduce you to Monasca analytics, a seamless extension of Monanas that enables sharing of infrastructure analytic recipes across the community. Some of you are probably already familiar with it after we, in a "well-orchestrated marketing campaign", pushed

Re: [openstack-dev] [keystone][docs] API sprint results

Congrats to the team, what an effort! Thanks so much for putting this together. Anne On Fri, Jul 15, 2016 at 9:08 AM, Steve Martinelli wrote: > First of all, thanks to everyone who participated, the API sprint was a huge > success. We've converted nearly all of our old

[openstack-dev] [keystone][docs] API sprint results

First of all, thanks to everyone who participated, the API sprint was a huge success. We've converted nearly all of our old APIs (published on specs.openstack.org) over to the proper API site ( http://developer.openstack.org/api-ref.html). We've got a few patches in flight, and a few TODOs that

Re: [openstack-dev] [openstack-ansible] Project Mascot

Hi Jesse, I like the idea of a water buffalo, as they're working animals used in farming etc. This links nicely to the project as these animals 'do the heavy lifting', so to speak. An ox, etc. could be another appropriate mascot. --Matt On Fri, Jul 15, 2016 at 2:15 PM, Jesse Pretorius <

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

+1 On 15.07.16 16:25, Tatyana Leontovich wrote: +1 On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova > wrote: +1 On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy

Re: [openstack-dev] [release][documentation][telemetry][murano][trove] missing milestones

Doug, At this time it is highly unlikely that there will be a 0b2 tag on trove-image-builder. I may get to a 0b3 tag but per the proposed membership freeze[1], we have missed two of the milestones and therefore trove-image-builder will likely not be included in the newton release. Thanks,

[openstack-dev] [release][documentation][telemetry][murano][trove] missing milestones

We have a few deliverables without any milestone tags for this release cycle, yet (see the list below). They are at risk of being excluded from the final release for failing to prepare releases under the cycle-with-milestone release model. Please propose 0b2 tags by the end of the day, or let us

Re: [openstack-dev] [kolla] our mascot - input needed

On 15/07/16 03:53, Britt Houser (bhouser) wrote: Koala is the best by a long shot. These ideas are all total stretches: Bee on a honeycomb – Its kinda like the bee is orchestrating containers of honey. That sounds more like a honeypot ant to me: https://en.wikipedia.org/wiki/Honeypot_ant

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

+1 On Fri, Jul 15, 2016 at 4:08 PM, Anastasia Urlapova wrote: > +1 > > On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy < > asledzins...@mirantis.com> wrote: > >> Hi, >> I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops [1] >> core. >> >> Alexey is

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

+1 Regards, Bulat Gaifullin Mirantis Inc. > On 15 Jul 2016, at 16:08, Anastasia Urlapova wrote: > > +1 > > On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy > > wrote: > Hi, > I'd like to nominate Alexey

[openstack-dev] [openstack-ansible] Project Mascot

Hi everyone, As discussed in the community meeting yesterday [1] the foundation wishes each project to select a mascot for the project [2][3]. The mascot needs to be appropriate (please read the links for the constraints) and in some way linked to the project. We need to come up with a list of

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

+1 On Fri, Jul 15, 2016 at 4:02 PM, Andrey Sledzinskiy < asledzins...@mirantis.com> wrote: > Hi, > I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops [1] > core. > > Alexey is doing great job improving fuel-qa and fuel-devops projects. > He's become an expert in code base in

[openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

Hi, I'd like to nominate Alexey Stepanov for fuel-qa [0] and fuel-devops [1] core. Alexey is doing great job improving fuel-qa and fuel-devops projects. He's become an expert in code base in very short terms so I think he deserves to be a part of fuel-qa/fuel-devops core team. Please, vote for

Re: [openstack-dev] [heat][yaql] Heat map replacement options

On Fri, Jul 15, 2016 at 03:35:51PM +0300, Peter Razumovsky wrote: >Try this: >yaql: >  expression:let(root => $) -> >dict($root.data.service.items().select([$[0], $root.data.ip[$[1]]])) >  data: >    service: { get_param: ServiceNetMap } >    ip: { get_param: NetIpMap}

Re: [openstack-dev] [heat][yaql] Heat map replacement options

Try this: yaql: expression:let(root => $) -> dict($root.data.service.items().select([$[0], $root.data.ip[$[1]]])) data: service: { get_param: ServiceNetMap } ip: { get_param: NetIpMap} 2016-07-15 12:25 GMT+03:00 Steven Hardy : > Hi all, > > I'm trying to figure

Re: [openstack-dev] [Openstack] Filter ComputeCapabilitiesFilter returned 0 hosts

When I setup my host aggregates, and want to direct a flavor to a specific aggregate I use the following steps. nova aggregate-set-metadata aggregate1 hiperf=true nova flavor-key flavor1 set aggregate_instance_extra_specs:hiperf=true in your case.. nova aggregate-set-metadata zfs

Re: [openstack-dev] [kolla][nova][infra] Voting gates

On Thu, Jul 14, 2016 at 03:19:39PM -0500, Matt Riedemann wrote: > On 7/14/2016 11:34 AM, Paul Bourke wrote: > > Hi Matt, > > > > Here is the failure from nova_compute on trying to start an instance: [...] > > 2016-07-13 18:04:12.634968 | 2016-07-13 18:01:34.560 1 ERROR > > oslo_service.service

Re: [openstack-dev] [neutron][qos][drivers] RFE about QoS extended validation

Oh yikes, I was "hit by a plane" (delay) plus a huge jet lag and didn't make it to the meeting, I'll be there next week. Thank you. On Tue, Jul 12, 2016 at 9:48 AM, Miguel Angel Ajo Pelayo wrote: > I'd like to ask for some prioritization on this RFE [1], since it's blocking

Re: [openstack-dev] [Openstack] 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

Re: [openstack-dev] [Openstack] Filter ComputeCapabilitiesFilter returned 0 hosts

On Jul 14, 2016, at 11:15 PM, Brent Troge wrote: > dont you have to set something like the below in your flavor ? > > aggregate_instance_extra_specs:volume_type=ZOL If you mean properties:volume_type=ZOL then yes. But is the "aggregate_instance_extra_specs" something specific, or

Re: [openstack-dev] [OPENSTACK] [HORIZON] Changing theme

No, i did run it. In the first run it collected some files but later run it didn't (maybe as it already collected). Also after deleting "/us/share/openstack-dashboard-ubuntu-theme" if i run collectstatic then it is giving error with

Re: [openstack-dev] [OPENSTACK] [HORIZON] Changing theme

No, i did run it. In the first run it collected some files but later run it didn't (maybe as it already collected). Also after deleting "/us/share/openstack-dashboard-ubuntu-theme" if i run collectstatic then it is giving error with

Re: [openstack-dev] [OPENSTACK] [HORIZON] Changing theme

Did you forget to run collectstatic? On Fri, Jul 15, 2016 at 10:00 AM, BIKRAMADITYA SAHOO < ansh.ansh20...@gmail.com> wrote: > Hi, > > I am unable to change the theme for my openstack horizon. I tried with the > this and >

[openstack-dev] [heat][yaql] Heat map replacement options

Hi all, I'm trying to figure out the cleanest way to do a replacement of values in a mapping (json parameter) in a heat template, e.g: ServiceNetMap: type: json default: IronicApiNetwork: internal_api CephPublicNetwork: storage NetIpMap: type: json default:

Re: [openstack-dev] [nova][scheduler] A simple solution for better scheduler performance

On 15 July 2016 at 09:26, Cheng, Yingxin wrote: > It is easy to understand that scheduling in nova-scheduler service consists > of 2 major phases: > A. Cache refresh, in code [1]. > B. Filtering and weighing, in code [2]. > > Couple of previous experiments [3] [4] shows

[openstack-dev] [TripleO][release] TripleO Newton Release schedule and Feature Freeze

Hi all, So we discussed $subject in our weekly meeting, and I wanted to follow up with some proposals to clarify our plan wrt the final Newton release, feature freeze, and how the dates will line up given that we're now following[1] the cycle-trailing release model[2] for most TripleO

[openstack-dev] [OPENSTACK] [HORIZON] Changing theme

Hi, I am unable to change the theme for my openstack horizon. I tried with the this and various other tutorial but i am still unable to achieve my goal. I also want to have a custom "splash" (a complete custom login) and i am

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Hi, Le 13/07/2016 à 21:17, Denis Makogon a écrit : I have free capacity to work on porting code to Py3. So, if any PTL is running out of team capacity i can help to work on project to enable Py3 support. If you would like to help, you can try to run functional tests on DevStack. Begin with

Re: [openstack-dev] [TripleO] 3rd party CI

On Thu, Jul 14, 2016 at 04:45:03PM -0400, Wesley Hayutin wrote: >Greetings, >Just wanted to let folks know we're bringing up two 3rd party gates for >TripleO CI atm. >1. The first gate will be for upgrading from mitaka -> newton/master >2. The second gate will be for running

Re: [openstack-dev] [Openstack] 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

Re: [openstack-dev] [TripleO] Making TripleO CI easier to consume outside of TripleO CI

On Tue, Jul 12, 2016 at 03:39:41PM -0400, John Trowbridge wrote: > Howdy folks, > > In the TripleO meeting two weeks ago, it came up that tripleo-quickstart > is being used as a CI tool in RDO. This came about organically, because > we needed to use RDO CI to self-gate quickstart (it relies on

Re: [openstack-dev] [TripleO][os-net-config] add support for NFV virtual switch

On Tue, Jul 12, 2016 at 04:38:49PM -0500, Ben Nemec wrote: > On 07/07/2016 05:45 PM, Xin Wu wrote: > > Hi, > > > > This is Xin from Big Switch. I'm proposing to make os_net_config support > > DPDK switch for NFV workloads. > > Current os_net_config supports ovs_bridge, linux_bridge,

[openstack-dev] [nova][scheduler] A simple solution for better scheduler performance

It is easy to understand that scheduling in nova-scheduler service consists of 2 major phases: A. Cache refresh, in code [1]. B. Filtering and weighing, in code [2]. Couple of previous experiments [3] [4] shows that “cache-refresh” is the major bottleneck of nova scheduler. For example, the

[openstack-dev] [OPENSTACK] [HORIZON] Changing theme

Hi, I am unable to change the theme for my openstack horizon. I tried with the this and various other tutorial but i am still unable to achieve my goal. I also want to have a custom "splash" (a complete custom login) and i am