Hi all,
I have two points.
a. For the problem in this thread, my suggestion is to introduce new
concepts to replace the existing firewall and SG.
Perhaps you have found the overlap between firewall and SG. It's trouble
for user to select.
So the new concepts are edge-firewall for N/S traffic and D
Let's get these details into the QuickStart doc so anyone else hitting this can
be clued in.
--
Adrian
On Aug 27, 2015, at 9:38 PM, Vikas Choudhary
mailto:choudharyvika...@gmail.com>> wrote:
Hi Stanislaw,
I also faced similar issue.Reason might be that from inside master instance
openstack
Thanks everyone for the feedback!
There weren't any comments about options (1) and (4), I'm interpreting
it as a consensus that we're not doing a "future" branch, and as a sign
that nobody wants to even think about CI for external forks (which I'm
sure will come back to haunt us, so don't count o
Hi,
I've been running against openstack-dev (master branch) using the
stackforge/networking-ovs-dpdk master branch (OVS GIT TAG
1e77bbe565bbf5ae7f4c47f481a4097d666d3d68), using the single-node local.conf
file on Ubuntu 15.04. I've had to patch a few things to get past ERRORs during
start:
- di
Hi Stanislaw,
I also faced similar issue.Reason might be that from inside master
instance openstack heat service is not reachable.
Please check /var/log/cloud-init-log for any connectivity related
error message and if found try manually whichever command has failed
with correct url.
If this is
> > Hi
> >
> > With keystone, we recently came across an issue in terms of the assumptions
> > that the openstack client is making about the
> > entities it can show - namely that is assumes all entries have a ‘name’
> > attribute (which is how the "openstack show"
> > command works). Turns out,
Chen, Wei D would like to recall the message, "[openstack-dev]
[api][keystone][openstackclient] Standards for object name attributes and
filtering".
__
OpenStack Development Mailing List (not for usage questions)
Unsubscrib
> On Aug 26, 2015, at 4:45 AM, Henry Nash wrote:
>
> > Hi
> >
> > With keystone, we recently came across an issue in terms of the assumptions
> > that the openstack client is making about the
> entities it can show - namely that is assumes all entries have a 'name'
> attribute (which is how the
> Hi
>
> With keystone, we recently came across an issue in terms of the assumptions
> that the openstack client is making about the
> entities it can show - namely that is assumes all entries have a ‘name’
> attribute (which is how the "openstack show"
> command works). Turns out, that not all
hi folks:
When we use paginated queries to retrieve instances, we can't get the
total count of instances in current list-servers API.
The count of the querying result is important for operators, Think about a
case, the operators want to know how many 'error' instances
in current deployment in
On Fri, Aug 28, 2015 at 11:12:43AM +1200, Robert Collins wrote:
> I'm pretty sure it *will* be EOL'd. OTOH thats 10 weeks of fixes folk
> can get. I think you should do it if you've the stomach for it, and if
> its going to help someone. I can aid by cutting library releases for
> you I think (hav
On 8/27/2015 2:38 PM, Ben Swartzlander wrote:
Manila recently implemented microversions, copying the implementation
from Nova. I really like the feature! However I noticed that it's legal
for clients to transmit "latest" instead of a real version number.
THIS IS A TERRIBLE IDEA!
I recommend r
Hi,
As (most of) you are aware, in this cycle, ironic decided to switch to a
feature-based release model[0].
Our first semver release, 4.0.0, was tagged this week but a few more things
need to be ironed out still (hopefully there will be an announcement about
that in the near future).
What I wan
Do you have a known good commit for the FwaaS repo? Or Neutron? Perhaps you can
run a git-bisect to find the commit that introduced. Labor intensive, but I did
a little digging in FwaaS and didn't see anything that was obvious.
--
Sent from my Android device with K-9 Mail. Please excuse my brevi
Hi ,
Adding more info
create_firewall(self, agent_mode, apply_list, firewall) and
update_firewall(self, agent_mode, apply_list, firewall) api's are
getting called with empty apply list
apply_list is generated by the _get_router_info_list_for_tenant. The
rootcause for returning empty list is
Hi
I have been running some rally tests against convergence and our existing
implementation to compare.
So far I have done the following:
1. defined a template with a resource group
https://github.com/asalkeld/convergence-rally/blob/master/templates/resource_group_test_resource.yaml.templ
TL/DR: Do you have an opinion on language style? Of course you do! Come
weigh in on javascript style rules!
https://review.openstack.org/#/q/status:open+project:openstack/eslint-config-openstack,n,z
(List will continually update as we add more patches)
The original introducti
On 2015-08-27 1:23 PM, Tim Bell wrote:
>
> Some project such as cinder include a detailed description option where
> you can include an arbitrary string with a volume to remind the admins
> what the volume is used for.
>
> Has anyone looked at doing something similar for Nova for instances and
>
On 8/27/2015 12:23 PM, Tim Bell wrote:
Some project such as cinder include a detailed description option where
you can include an arbitrary string with a volume to remind the admins
what the volume is used for.
Has anyone looked at doing something similar for Nova for instances and
Glance for
Hi, Sean,
Dnsmasq is managed by Cobbler. Cobbler may also manage isc-dhcpd + BIND
[0]. So, switching from dnsmasq requires 2 more services been installed. I
think it's not a big deal to a update Cobbler container. The most work will
be in adding ipv6 support into everything: fuelmenu, Nailgun/UI,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'd like to announce that we have stamped stable/kilo.
I'd like to congratulate everyone who has committed and helped the
OpenStack-Chef project get to this milestone.
We have made tremendous progress with the limited resources our project has.
I
On 27 August 2015 at 10:32, Tony Breeds wrote:
> No problem. It seemed like such a simple thing :/
Hah. No :/. Its at the very core of the issues we've had with distros
packaging Kilo, and we had with the opening of Liberty, and the rework
of the plumbing here I've been leading for the last cyc
Thanks Jeremy!
On 8/27/15 5:10 PM, Jeremy Stanley wrote:
> On 2015-08-26 12:48:23 -0400 (-0400), Nikhil Komawar wrote:
>> Can't find the logs on eavesdrop atm. Discussed yesterday on
>> #openstack-relmgr-office around UTC evening.
> http://eavesdrop.openstack.org/irclogs/%23openstack-relmgr-offic
Ok. Can you add a git log -n 1? It would be nice to positively confirm the
patch under test is being used:
e.g.
http://ci-openstack.storpool.com:8080/job/dsvm-tempest-storpool-cinder-driver/3129/console.log
points to:
Triggered by: https://review.openstack.org/217802 patchset 1: iSCSI fix
m
Hello all,
I wanted to share my thoughts about the recent patch which I submitted
https://review.openstack.org/#/c/217377/.
Abstract of the patch: it removes the encryption of default parameters when
running `heat-manage update_params encrypt`.
Firstly, the current encrypt/decrypt behavior is
On Fri, Aug 28, 2015 at 12:22 AM, Asselin, Ramy wrote:
> Hi Peter,
>
> Your log files require downloads. Please fix it such that they can be viewed
> directly [1]
Hi, and thanks for the fast reply! Yes, I'll try to change the
webserver's configuration, although the snippet in the FAQ won''t hel
Excerpts from Matt Riedemann's message of 2015-08-27 15:50:13 -0500:
>
> On 8/25/2015 9:15 AM, Matt Riedemann wrote:
> >
> >
> > On 8/20/2015 6:12 AM, Eduard Matei wrote:
> >> Hi,
> >>
> >> ATM our workaround is to manually pip install futures==2.2.0 before
> >> running stack.sh
> >>
> >> Any idea
On 28/08/15 00:53, Rich Megginson wrote:
> On 08/27/2015 07:00 AM, Gilles Dubreuil wrote:
>>
>> On 27/08/15 22:40, Gilles Dubreuil wrote:
>>>
>>> On 27/08/15 16:59, Gilles Dubreuil wrote:
On 26/08/15 06:30, Rich Megginson wrote:
> This concerns the support of the names of domain sco
On 2015-08-27 13:55:16 -0700 (-0700), Vahid S Hashemian wrote:
> Thank you for your response. What you suggested makes sense. Could
> you please also confirm
>
> - Whether you push your work in progress to review.openstack.org
> and go to the site and manually mark it as "work in progress" (so
> r
Hi Peter,
Your log files require downloads. Please fix it such that they can be viewed
directly [1]
Also, it's not clear where in your scripts you actually pull down the cinder
patch.
Ramy
[1]
http://docs.openstack.org/infra/system-config/third_party.html#faq-frequently-asked-questions
---
The full results of lastcomment script are here for last 400 commits: [1][2]
[1] http://paste.openstack.org/show/430074/
[2] http://paste.openstack.org/show/430088/
From: Angela Smith
Sent: Thursday, August 27, 2015 1:56 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: DL-
Hello,
I'm a new developer on the Openstack project and am in the process of creating
live migration CI for HP's 3PAR and Lefthand backends. I noticed you guys are
looking for someone to pick up Joe Gordon's change for volume backed live
migration tests and we can sure use something like this.
On 2015-08-26 12:48:23 -0400 (-0400), Nikhil Komawar wrote:
> Can't find the logs on eavesdrop atm. Discussed yesterday on
> #openstack-relmgr-office around UTC evening.
http://eavesdrop.openstack.org/irclogs/%23openstack-relmgr-office/%23openstack-relmgr-office.2015-08-24.log.html#t2015-08-24T14:
Hi Jeremy,
Thank you for your response. What you suggested makes sense. Could you
please also confirm
- Whether you push your work in progress to review.openstack.org and go to
the site and manually mark it as "work in progress" (so reviewers don't
assume it's ready for review)?
- When you pul
Mike,
An update on Brocade CI progress. We are now using the format required for
results to show in lastcomment script.
We have been consistently reporting for last 9 days. See results here: [1].
We are still working on resolving recheck issue and adding link to wiki page in
the failed result c
On 8/25/2015 9:15 AM, Matt Riedemann wrote:
On 8/20/2015 6:12 AM, Eduard Matei wrote:
Hi,
ATM our workaround is to manually pip install futures==2.2.0 before
running stack.sh
Any idea when an "official" fix will be available?
Thanks,
Eduard
__
Hi,
Some time ago I sent
http://lists.openstack.org/pipermail/third-party-announce/2015-August/000261.html
to the third-party-announce list as a reply to a message about the
StorPool Cinder third-party CI being disabled. Well, as I wrote in my
reply there, I think that we have done what Mike Pere
On 2015-08-27 12:14:29 -0700 (-0700), Vahid S Hashemian wrote:
[...]
> I have a development folder for murano under
> /home/stack/workspace/murano. If the changes I make involve
> multiple files I would have to remember each time what files were
> changes to make sure I copy them over under /opt/st
I was looking over the admin guide
http://docs.openstack.org/admin-guide-cloud/networking_config-agents.html#configure-l3-agent
and noticed this:
"If you reboot a node that runs the L3 agent, you must run the
neutron-ovs-cleanup command before the neutron-l3-agent service starts".
Taking a loo
On Thu, Aug 27, 2015 at 11:47 AM, Everett Toews wrote:
> On Aug 26, 2015, at 4:45 AM, Henry Nash wrote:
>
> > Hi
> >
> > With keystone, we recently came across an issue in terms of the
> assumptions that the openstack client is making about the entities it can
> show - namely that is assumes all
I would say to extend murano with additional capabilities.
Dependency management for composite applications is very important for
modern development so, I think, adding additional use-cases could be very
benifitial for Murano.
On Aug 27, 2015 2:53 PM, "Nikolay Starodubtsev"
wrote:
> Dmitry,
> Doe
Hi,
In a previous message[1] I described a plan for moving projects in the
stackforge/ git namespace into openstack/.
We have scheduled this migration for Saturday October 17, 2015.
If you are responsible for a stackforge project, please visit the
following wiki page as soon as possible and add
Manila recently implemented microversions, copying the implementation
from Nova. I really like the feature! However I noticed that it's legal
for clients to transmit "latest" instead of a real version number.
THIS IS A TERRIBLE IDEA!
I recommend removing support for "latest" and forcing client
hi,
there has been a lot of work done across the community and Ceilometer
relating to versionedobjects. in Ceilometer particularly, this effort
has somewhat stalled as contributors are unsure of the benefits of
versionedobjects and how it relates to Ceilometer. there was a little
skeptism bec
As a part of our continued effort to make the v2 primary API and get
people to consume it without confusion we are planning to move ahead
with the client release (the release would set the default version of
API to 2). There haven't been any major/minor raised here.
An issue regarding the possibl
Hi,
On Thu, Aug 27, 2015 at 5:43 PM, Clint Byrum wrote:
> Excerpts from Lucas Alvares Gomes's message of 2015-08-27 02:40:26 -0700:
>> On Wed, Aug 26, 2015 at 11:09 PM, Julia Kreger
>> wrote:
>> > My apologies for not expressing my thoughts on this matter
>> > sooner, however I've had to spend s
Hi Victor,
You are awesome! Thank you. I took your recommendation and was able to set
up a virtualenv with the local python-muranoclient and saw a simple change
I made when running the murano command.
I think I have everything I need now to start working on patches.
I just have an efficiency qu
On 08/27/2015 08:43 PM, Douglas Fish wrote:
I took a quick look at the projects Daisy listed. None of them are ready
to be translated yet.
*Manila UI and Tuskar UI*
These projects don't have PO/POT files yet. In order to be ready they
need to start with step 1 from Daisy's note.
*Horizon Cisco
Hi,
I wanted to ask if we have any opinions on dnsmasq, since I am doing
some hacking on adding IPv6 support to fuel, for the provisioning stage.
https://review.openstack.org/#/c/216787/
Depending on if dnsmasq supports DHCPv6 options for PXE booting, we may
need to investigate replacing it with
On Aug 26, 2015, at 4:45 AM, Henry Nash wrote:
> Hi
>
> With keystone, we recently came across an issue in terms of the assumptions
> that the openstack client is making about the entities it can show - namely
> that is assumes all entries have a ‘name’ attribute (which is how the
> "openstac
I took a quick look at the projects Daisy listed. None of them are ready to
be translated yet.
Manila UI and Tuskar UI
These projects don't have PO/POT files yet. In order to be ready they need
to start with step 1 from Daisy's note.
Horizon Cisco UI
Has a locale file
https://github.com/openstack
If you want my inexperienced opinion, a young project is the perfect
time to start this. Nova has had a bunch of problems with versioned
objects that don't get realized until the next release (because that's
the point in time at which grenade (or worse, operators) catch this). At
that point, yo
That could be done but we'd need to establish an agreed name so that Horizon or
the CLIs, for example, could filter based on description. "Give me all VMs with
Ansys in the description".
If we use properties, a consistent approach would be needed so the higher level
tooling could rely on it (an
Excerpts from Thierry Carrez's message of 2015-08-27 11:20:05 +0200:
> Doug Hellmann wrote:
> > Excerpts from Robert Collins's message of 2015-08-19 11:04:37 +1200:
> >> Proposed data structure:
> >> - create a top level directory in each repo called release-notes
> >> - within that create a subdir
On 08/27/2015 10:43 AM, Ivan Kolodyazhny wrote:
Hi,
Looks like we need to be able to set AZ per backend. What do you think
about such option?
I dislike such an option.
The whole premise behind an AZ is that it's a failure domain. The node
running the cinder services is in exactly one such f
Hello,
I'm John Villalovos aka jlvillal on IRC. I am working primarily on the Ironic
project and have been asked to work on functional testing for Ironic.
My main starting focus will be the openstack/python-ironicclient and
openstack/ironic projects.
I am trying to find out who else would be i
2015-08-27 18:43 GMT+02:00 Clint Byrum :
> Excerpts from Lucas Alvares Gomes's message of 2015-08-27 02:40:26 -0700:
> > On Wed, Aug 26, 2015 at 11:09 PM, Julia Kreger
> > wrote:
> > > My apologies for not expressing my thoughts on this matter
> > > sooner, however I've had to spend some time col
It's not needed for 2.6 either - unit test 2 includes a more up to date
discover implementation.
On 28 Aug 2015 5:21 am, "Matt Riedemann" wrote:
>
>
> On 8/27/2015 6:26 AM, Chandan kumar wrote:
>
>> Hello,
>>
>> I am packaging 'discover' module <
>> https://bugzilla.redhat.com/show_bug.cgi?id=125
On 8/25/2015 9:14 AM, Matt Riedemann wrote:
Support to change the admin password on an instance via the libvirt
driver landed in liberty [1] but the hypervisor support matrix wasn't
updated [2]. There is a version restriction in the driver that it won't
work unless you're using at least libvir
On 8/27/2015 13:23, Tim Bell wrote:
>
>
>
> Some project such as cinder include a detailed description option
> where you can include an arbitrary string with a volume to remind the
> admins what the volume is used for.
>
>
>
> Has anyone looked at doing something similar for Nova for instances
Some project such as cinder include a detailed description option where you can
include an arbitrary string with a volume to remind the admins what the volume
is used for.
Has anyone looked at doing something similar for Nova for instances and Glance
for images ?
In many cases, the names get
On 8/27/2015 6:26 AM, Chandan kumar wrote:
Hello,
I am packaging 'discover' module <
https://bugzilla.redhat.com/show_bug.cgi?id=1251951 > for RDO.
Since, this module is not maintained yet as per this
http://code.google.com/p/unittest-ext/
and this module is used as a test-dependencies in all
On 8/26/2015 6:20 PM, Michael Davies wrote:
Hey Everyone,
John Villalovos and I have been acting as the Nova-Ironic liaisons,
which mostly means dealing with bugs that have been raised against the
Ironic driver in Nova. So you can understand what we’ve been doing, and
how you can help us do th
On Friday, September 11 at 23:00 UTC Gerrit will be unavailable for
about 30 minutes while we rename some projects.
Existing reviews, project watches, etc, should all be carried
over. Currently, we plan on renaming the following projects:
stackforge/os-ansible-deployment -> openstack/openstack-
Excerpts from Lucas Alvares Gomes's message of 2015-08-27 02:40:26 -0700:
> On Wed, Aug 26, 2015 at 11:09 PM, Julia Kreger
> wrote:
> > My apologies for not expressing my thoughts on this matter
> > sooner, however I've had to spend some time collecting my
> > thoughts.
> >
> > To me, it seems lik
Everett Toews wrote:
> The following API guidelines are ready for cross project review. They will be
> merged on Sept. 4 if there's no further feedback.
>
> 1. Add description of pagination parameters
> https://review.openstack.org/#/c/190743/
>
> 2. Require "OpenStack-" in headers
> https://rev
Hi,
while testing the fwaas , i found router_info is not getting updated.
list awlays seems to be empty and getting updated only after the restart
of fw agent.
This issue resulting empty list while calling
_get_router_info_list_for_tenant.
i can see some comments as *"for routers without
Hi All,
The following API guidelines are ready for cross project review. They will be
merged on Sept. 4 if there's no further feedback.
1. Add description of pagination parameters
https://review.openstack.org/#/c/190743/
2. Require "OpenStack-" in headers
https://review.openstack.org/#/c/215683
Bump
The FWaaS team would really like some feedback from the DVR side.
Mickey
-Mickey Spiegel/San Jose/IBM wrote: -
To: openstack-dev@lists.openstack.org
From: Mickey Spiegel/San Jose/IBM
Date: 08/19/2015 09:45AM
Subject: [fwaas][dvr] FWaaS with DVR
Currently, FWaaS behaves differently
Akihiro, can you look at the developer's reference I posted (191944), where
there is the overall API plan and a proposal for handling backward
compatibility.
Thanks!
Paul Michali (pc_m)
On Thu, Aug 27, 2015 at 11:12 AM Akihiro Motoki wrote:
> As Mathias said, Horizon worked (and in many cases
I pushed a patch for Congress dependent on your patch.
https://review.openstack.org/#/c/217765/
Tim
On Thu, Aug 27, 2015 at 8:05 AM Sergey Lukjanov
wrote:
> Hi,
>
> I think filing the cross-project bug is ok. I've already uploaded patch
> for sahara jobs - https://review.openstack.org/217751
>> - SME reviews the code within SLA, which should be defined per component
Also I would like to add, that I'm not against of metrics, we can collect
metrics, in order to figure out if some improvement in the process helped
to speed up reviews, but asking Cores/SMEs to do the job faster will
defin
As Mathias said, Horizon worked (and in many cases works) cross releases.
Horizon determines supported features based on keystone catalogs,
extension list from back-end services (like nova, neutron).
Micro-versioning support may come in future (though it is not supported).
For backward incompatib
Hi,
I think filing the cross-project bug is ok. I've already uploaded patch for
sahara jobs - https://review.openstack.org/217751
Thanks.
On Wed, Aug 26, 2015 at 6:46 PM, Chris Dent wrote:
>
> [If any of this is wrong I hope someone from infra or qa will
> correct me. Thanks. This feels a bit
There were a little IRC discussion on that [1] and I've started to work on
creating a spec for Mitaka. I've got a little busy last time, but finishing it
is still in my backlog. I'll make sure to post it up for reviews once Mitaka
specs bucket will open.
[1]
http://eavesdrop.openstack.org/ircl
Hi Mike,
I have several comments.
>> SLA should be the driver of doing timely reviews, however we can’t allow
to fast-track code into master suffering quality of review ...
As for me the idea of SLA contradicts to qualitative reviews.
Another thing is I got a bit confused by the difference betw
Mike,
speaking of automation, AFAIK Boris Pavlovic introduced some scripts
in Rally which do basic preliminary check of review message, checking
that it's formally correct. It should make life of reviewers a bit
easier, you might want to introduce them in Fuel as well, if not yet.
Regards,
Igor Mar
On 08/27/2015 07:00 AM, Gilles Dubreuil wrote:
On 27/08/15 22:40, Gilles Dubreuil wrote:
On 27/08/15 16:59, Gilles Dubreuil wrote:
On 26/08/15 06:30, Rich Megginson wrote:
This concerns the support of the names of domain scoped Keystone
resources (users, projects, etc.) in puppet.
At the p
-1 from me.
IMHO, the rolling upgrade feature makes sense for a mature project (like Nova),
but not for a young project like Magnum. It incurs overheads for contributors &
reviewers to check the object compatibility in each patch. As you mentioned,
the key benefit of this feature is supporting
Hi,
Looks like we need to be able to set AZ per backend. What do you think
about such option?
Regards,
Ivan Kolodyazhny
On Mon, Aug 10, 2015 at 7:07 PM, John Griffith
wrote:
>
>
> On Mon, Aug 10, 2015 at 9:24 AM, Dulko, Michal
> wrote:
>
>> Hi,
>>
>> In Kilo cycle [1] was merged. It started p
Hi,
I'm all in for any formalization and automation of review process. The only
concern that I see here is about core reviewers involvement metrics. If we
succeed in reducing the load on core reviewers, it will mean that core
reviewers will do less code reviews. This could lead to core reviewer
de
Mike,
This is a great start.
1) I'd advise to codify a proposal in fuel-specs under a 'policy' directory
(obviously as a review in fuel-specs repo) So everyone agrees to the
structure of the teams and terminology etc. Example oslo uses a directory
to write down some of our decisions.
http://git.o
On 8/25/15, 10:58, "Clay Gerrard" wrote:
>
>
>On Tue, Aug 25, 2015 at 8:45 AM, Kevin L. Mitchell
> wrote:
>
>On Mon, 2015-08-24 at 22:53 -0700, Clay Gerrard wrote:
>> So, I know that hacking has H301 (one import per line) - but say maybe
>> you wanted to import *more* that one thing on a line (
[2] is the best option to upload the image.
Yes, the install_master.sh script manually runs puppet to apply your dev
changes to nodepool.yaml and vars.sh to your production configuration (e.g.
/etc/nodepool/nodepool.yaml).
Ramy
From: Abhishek Shrivastava [mailto:abhis...@cloudbyte.com]
Sent: W
On 27/08/15 22:40, Gilles Dubreuil wrote:
>
>
> On 27/08/15 16:59, Gilles Dubreuil wrote:
>>
>>
>> On 26/08/15 06:30, Rich Megginson wrote:
>>> This concerns the support of the names of domain scoped Keystone
>>> resources (users, projects, etc.) in puppet.
>>>
>>> At the puppet-openstack meeti
Thanks for the links and thoughtful comments James!
In the Heat documentation, is the subnet ID being treated as optional (or
is the documentation not correct)? I think it is a required argument in the
REST API. Ref:
http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Neutro
On 27/08/15 16:59, Gilles Dubreuil wrote:
>
>
> On 26/08/15 06:30, Rich Megginson wrote:
>> This concerns the support of the names of domain scoped Keystone
>> resources (users, projects, etc.) in puppet.
>>
>> At the puppet-openstack meeting today [1] we decided that
>> puppet-openstack will s
Hi Henry
in principle I think it is a good idea to have a user friendly name
attribute for every entity. The name should be unique amongst the same
set of entities (though not between entities since context should imply
what entity you are referring to), otherwise the name would have to be
combine
Dmitry,
Does I understand properly and your recommendation is to change some murano
logic?
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
2015-08-24 23:31 GMT+03:00 Dmitry :
> I think that you can model application dependencies in a way it will allow
> multi-s
> -Original Message-
> From: Eric Harney [mailto:ehar...@redhat.com]
> Sent: Wednesday, August 26, 2015 5:15 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [grenade][cinder] Updates of rootwrap filters
>
> On 08/26/2015 09:57 AM, Dulko,
Hello,
I am packaging 'discover' module <
https://bugzilla.redhat.com/show_bug.cgi?id=1251951 > for RDO.
Since, this module is not maintained yet as per this
http://code.google.com/p/unittest-ext/
and this module is used as a test-dependencies in all the projects as per
'openstack-requirements' mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/27/2015 12:05 PM, bharath wrote:
> Hi,
>
> Liberty code freeze is September 1st. But i have to add a vendor
> specific table for liberty release . As Vendor specific alembic
> support in neutron is seems to be still under progress. Can i
>
On Wed, 26 Aug 2015, Matthew Treinish wrote:
http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/functions.sh#n571
Is 'process_testr_artifacts' going to already be in scope for the
hook script or will it be necessary to source functions.sh to be
sure? If so, where is it?
--
Chris
In external.py are stored names of table that was already created in
Neutron, but then there models were moved to vendor repos. So adding new
names in external.py won't help you.
On Thu, Aug 27, 2015 at 1:05 PM, bharath wrote:
> Hi,
>
> Liberty code freeze is September 1st. But i have to add a v
Hi,
Can anyone answer:
How many compute nodes supported by a basic and an advanced high end hardware
configuration OpenStack controller.
Here I want to know the OpenStack service performance.
Thanks and Regards,
Raghavendrachari kamsali,
Embedded Computing and Power,
Hyderabad, AndhraPradesh
Hi,
Liberty code freeze is September 1st. But i have to add a vendor
specific table for liberty release . As Vendor specific alembic
support in neutron is seems to be still under progress. Can i
simply add tables names in external.py under alembic_migration and
push it upstream and implement ac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/27/2015 11:56 AM, Davanum Srinivas wrote:
> Daisuke,
>
> It's very late for merging these patches for Liberty. Sorry, they
> will have to wait till M. We can talk more about it on next
> Monday's Oslo meeting. Please let us know and i'll add a
Daisuke,
It's very late for merging these patches for Liberty. Sorry, they will have
to wait till M. We can talk more about it on next Monday's Oslo meeting.
Please let us know and i'll add a topic there if you can make it.
-- Dims
On Thu, Aug 27, 2015 at 1:04 AM, Fujita, Daisuke <
fuzita.dais..
On 08/27/2015 11:40 AM, Lucas Alvares Gomes wrote:
On Wed, Aug 26, 2015 at 11:09 PM, Julia Kreger
wrote:
My apologies for not expressing my thoughts on this matter
sooner, however I've had to spend some time collecting my
thoughts.
To me, it seems like we do not trust our users. Granted,
when
On Wed, Aug 26, 2015 at 11:09 PM, Julia Kreger
wrote:
> My apologies for not expressing my thoughts on this matter
> sooner, however I've had to spend some time collecting my
> thoughts.
>
> To me, it seems like we do not trust our users. Granted,
> when I say users, I mean administrators who lik
1 - 100 of 109 matches
Mail list logo
