Thanks for your response.
We have analysed the issue further and the DG is not the problem.
We have taken tcpdumps on all interfaces and we can see that the ping reaches
the VIP on the driver virtual appliance and the virtual appliance responds to
the ping. It responds with the mac address
Take up on this was a bit lower then I would have hoped but lets go
ahead with it anyways ;-)
we had 6 volunteers altogether.
I've taken the list of current tripleo bugs and split them into groups
of 15 (randomly shuffled) and assigned a group to each volunteer.
Each person should take a look
I can try to comment on your questions... inline @PCM
PCM (Paul Michali)
IRC pc_m (irc.freenode.com)
Twitter... @pmichali
On Tue, Jan 27, 2015 at 9:45 PM, shihanzhang ayshihanzh...@126.com wrote:
Hi Stacker:
I am a novice, I want use Neutron VPNaas, through my
Hi,
At the mid cycle meet up it was discussed that we need to prioritize the BP's
that require review. This will at least get us a chance of getting something
into Nova this cycle.
The following BP's are ready for review:
1. Ephemeral disk support -
Hi everyone,
When we first introduced the cross-project specs (specs for things that
may potentially affect all OpenStack projects, or where more convergence
is desirable), we defaulted to rather simple rules for approval:
- discuss the spec in a cross-project meeting
- let everyone +1/-1 and
Putting the right tag in the subject to see if somone can help answer the
below
thanx,
deepak
On Tue, Jan 27, 2015 at 7:57 PM, Bharat Kumar bharat.kobag...@redhat.com
wrote:
Hi,
I have seen Sean Dague's patch [1], if I understood correctly, by this
patch we can reduce the number of
Hi,
Approximately a year and a half ago, the default DHCP lease time in Neutron
was increased from 120 seconds to 86400 seconds.[1] This was done with the
goal of reducing DHCP traffic with very little discussion (based on what I
can see in the review and bug report). While it it does indeed
On Fri, 23 Jan 2015 16:53:55 +
Day, Phil philip@hp.com wrote:
Hi Folks,
Is there any support yet in novaclient for requesting a specific
microversion ? (looking at the final leg of extending
clean-shutdown to the API, and wondering how to test this in devstack
via the novaclient)
On 01/28/2015 09:50 AM, Kevin Benton wrote:
Hi,
Approximately a year and a half ago, the default DHCP lease time in
Neutron was increased from 120 seconds to 86400 seconds.[1] This was
done with the goal of reducing DHCP traffic with very little
discussion (based on what I can see in the
Quick top-post apology...
It's entirely possible that there are people who are reading these lists
who do not personally know me or my tendency to overuse hyperbole.
I would like to formally apologize for both the subject of this thread
and my use of the word autocratic. They are both
Oleg,
In 6.0 we build OS target images during Fuel ISO building and then we just
put them on the ISO. In 6.1 we are planning to build them (at least Ubuntu
one) on the master node. We deliberately don't use DIB because it is all
about cloud case. DIB downloads pre-built cloud images (ubuntu,
+1
On Tue, Jan 27 2015, Angus Salkeld wrote:
Hi all
After having a look at the stats:
http://stackalytics.com/report/contribution/heat-group/90
http://stackalytics.com/?module=heat-groupmetric=person-day
I'd like to propose the following changes to the Heat core team:
Add:
Qiming Teng
On Tue, Jan 27, 2015 at 10:26 PM, Gordon Sim g...@redhat.com wrote:
On 01/27/2015 06:31 PM, Doug Hellmann wrote:
On Tue, Jan 27, 2015, at 12:28 PM, Denis Makogon wrote:
I'd like to build tool that would be able to profile messaging over
various deployments. This tool would give me an
But without this separation on orchestration layer, we are unable to
differentiate between nodes.
What i mean is - we need to run subset of tasks on primary first and then
on all others, and we are using role as mapper
to node identities (and this mechanism was hardcoded in nailgun for a long
On Wed, Jan 28, 2015 at 11:36:41AM +1000, Angus Salkeld wrote:
Hi all
After having a look at the stats:
http://stackalytics.com/report/contribution/heat-group/90
http://stackalytics.com/?module=heat-groupmetric=person-day
I'd like to propose the following changes to the
On Fri, 23 Jan 2015 15:51:54 +0200
Andrey Kurilin akuri...@mirantis.com wrote:
Hi everyone!
After removing nova V3 API from novaclient[1], implementation of v1.1
client is used for v1.1, v2 and v3 [2].
Since we moving to micro versions, I wonder, do we need such
mechanism of choosing api
On 28/01/15 10:23 +0200, Denis Makogon wrote:
On Tue, Jan 27, 2015 at 10:26 PM, Gordon Sim g...@redhat.com wrote:
On 01/27/2015 06:31 PM, Doug Hellmann wrote:
On Tue, Jan 27, 2015, at 12:28 PM, Denis Makogon wrote:
I'd like to build tool that would be able to
Adam Lawson alaw...@aqorn.com writes:
Hi Adam,
I'm researching for a web-based visualization that simply displays
OpenStack Swift and/or node status, cluster health etc in some manner.
I wrote Swift Browser, which will let you browse the containers and
objects in your Swift cluster:
Monty Taylor wrote:
You'll notice that I did say in my suggestion that ANYONE should be able
to propose a name - I believe that would include non-dev people. Since
the people in question are marketing people, I would imagine that if any
of them feel strongly about a name, that it should be
Nik,
I'm now here and I don't agree that we need to remove changes
attribute. On the opposite, I think this is the only attribute which
should be looked at on UI and backend, and all these
pending_addition and pending_someotherstuff are obsolete and
needless.
You're absolutely right. It's
On 25/01/2015 11:00 PM, Ian Wells wrote:
Lots of open questions in here, because I think we need a long conversation
on the subject.
On 23 January 2015 at 15:51, Kevin Benton blak...@gmail.com wrote:
It seems like a change to using internal RPC interfaces would be pretty
unstable at this
Miguel Ángel Ajo
On Wednesday, 28 de January de 2015 at 09:50, Kevin Benton wrote:
Hi,
Approximately a year and a half ago, the default DHCP lease time in Neutron
was increased from 120 seconds to 86400 seconds.[1] This was done with the
goal of reducing DHCP traffic with very little
On Tue, 06 Jan 2015 07:31:19 -0500
Jay Pipes jaypi...@gmail.com wrote:
On 01/06/2015 06:25 AM, Chen CH Ji wrote:
Based on nova-specs api-microversions.rst
we support following function definition format, but it violate the
hacking rule pep8 F811 because duplicate function definition
we
+1
Regards,
Sergey.
On 28 January 2015 at 10:52, Pavlo Shchelokovskyy
pshchelokovs...@mirantis.com wrote:
+1
Pavlo Shchelokovskyy
Software Engineer
Mirantis Inc
www.mirantis.com
On Wed, Jan 28, 2015 at 8:26 AM, Thomas Herve thomas.he...@enovance.com
wrote:
Hi all
After having
On Mon, 05 Jan 2015 11:10:41 -0500
Jay Pipes jaypi...@gmail.com wrote:
Thoughts on getting consistency across all 3 projects (and possibly
others)?
Yeah, I personally like the second option as well, but agree that
consistency is the key (pun intended) here.
I would say let's make a
Hi,
*But with introduction of plugins and granular deployment, in my opinion,
we need to be able*
*to specify that task should run specifically on primary, or on
secondaries. Alternative to this approach would be - always run task on all
controllers, and let task itself to verify that it is
Hi,
we definitely need such separation on orchestration layer.
Is it possible to have significantly different sets of tasks for
controller and primary-controller?
Right now we already do different things on primary and secondary
controllers, but it's all conducted in the same manifest and
Hi All!
Thanks for the feedback!
I'll remove xattr from the requirements in my change set.
Currently i'm working on a workaround to execute 'getfattr' instead of the
xattr api call. We can asure getfattr is available via package dependencies
of our client who has to be installed either way.
I'm
+1 on all changes.
Regards,
Thomas
From: Angus Salkeld asalk...@mirantis.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 28/01/2015 02:40
Subject: [openstack-dev] [Heat] core team changes
Hi all
After having a look at the
Hello,
I want to use L3 functionalities with own device in place of normal
L3agent. So I think that best way will be to write own L3 service plugin
which will configure my router on my special device. But I don't know
now few things. For example if I'm creating new port in router
It's not clear what problem you are going to solve with putting serializers
alongside with deployment scripts/tasks.
I see two possible uses for specific serializer for tasks:
1. Compute additional information for deployment based not only on what is
present in astute.yaml
2. Request
+1 to replace simple to HA with one controller
/sv
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
On 27/01/15 13:22 -0500, Doug Hellmann wrote:
On Tue, Jan 27, 2015, at 12:44 PM, Julien Danjou wrote:
On Tue, Jan 27 2015, Clark Boylan wrote:
So the issue is that the garbage collector segfaults on null objects in
the to be garbage collected list. Which means that by the time garbage
Hi,
+1 for having primary-controller role in terms of deployment.
In our tasks user should be able to run specific task on primary-controller.
But I agree that it can be tricky because after the cluster is deployed, we
cannot say who is really primary, is there a case when it's important to
know
On 01/27/2015 10:35 PM, James E. Blair wrote:
Lauren Sell lau...@openstack.org writes:
Hey Monty,
I’d like to weigh in here, because I think there have been some
misunderstandings around Lemming-gate. I’m glad you raised your
concerns; it’s a good test of release naming for us all to
Igor,
But why can't we implement it properly on the first try? It doesn't
seem like a hard task and won't take much time.
On Wed, Jan 28, 2015 at 12:50 PM, Igor Kalnitsky
ikalnit...@mirantis.com wrote:
Nik,
I'm now here and I don't agree that we need to remove changes
attribute. On the
Hi Vladimir,
It's not clear what problem you are going to solve with putting serializers
alongside with deployment scripts/tasks.
For sure there is no way for this serializers to have access to the
database,
because with each release there will be a huge probability to get this
serializers broken
On Wed, Jan 28, 2015 at 11:39 AM, Flavio Percoco fla...@redhat.com wrote:
On 28/01/15 10:23 +0200, Denis Makogon wrote:
On Tue, Jan 27, 2015 at 10:26 PM, Gordon Sim g...@redhat.com wrote:
On 01/27/2015 06:31 PM, Doug Hellmann wrote:
On Tue, Jan 27, 2015, at 12:28 PM, Denis
Hello Vishvananda,
Initialize connection passes that data to cinder in the call. The connector
dictionary in the call should contain the info from nova:
https://github.com/openstack/cinder/blob/master/cinder/volume/driver.py#L1051
Ah yes, I see.
Thank you very much!
Regards,
Phil
--
:
On 2015-01-28 02:42:28 + (+), Douglas Mendizabal wrote:
Thanks for the heads up, and for adding the stable-compat-jobs to
the client. [1] This is an interesting problem, since the
proposal bot keeps the python-barbicanclient requirements in sync
with global-requirements. I’m not sure
Intel folks,
Belated welcome to Sahara! Thank you for your recent commits.
Moving this thread to openstack-dev so others may contribute, cc'ing
Daniele and Pietro who pioneered the Spark plugin.
I'll respond with another email about Oozie work, but I want to
address the Spark/Swift issue in
Hello,
I am trying to understand how a nova component can be run parallely on a
host. From the developer reference documentation it seems to indicate that
all the openstack services use green thread model of threading. Is it the
only model of parallelism for all the components or multiple
On 2015-01-28 23:37:18 +0800 (+0800), Tom Fifield wrote:
If logistics are getting complicated, is it necessary to lock it
down so much? I vaguely recall a launchpad poll in the past, which
was effectively open to the public? Is voting on the shortlisted
names something we should just open wide
James E. Blair wrote:
Considering that the process used to be
a poll of the ~openstack group on launchpad, it seemed like a fairly
straightforward mapping to ATCs. I wanted to find the easiest way to
get the most people in the community likely to vote as possible without
needing to generate
F811 is not part of our hacking lib - it's in flake8. As far as I know,
it's not possible to selectively disable that for particular files or
methods. And as mentioned earlier in the list and when I asked in
#openstack-dev the feeling was that we don't want to disable F811 globally
because it's
On Jan 28, 2015, at 7:05 AM, Steven Kaufer kau...@us.ibm.com wrote:
Vishvananda Ishaya vishvana...@gmail.com wrote on 01/27/2015 04:29:50 PM:
From: Vishvananda Ishaya vishvana...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
Monty Taylor wrote:
What if, to reduce stress on you, we make this 100% mechanical:
- Anyone can propose a name
- Election officials verify that the name matches the criteria
- * note: how do we approve additive exceptions without tons of effort
Devil is in the details, as reading some of
On Wed, Jan 28, 2015 at 9:52 AM, Salvatore Orlando sorla...@nicira.com wrote:
The patch Kevin points out increased the lease to 24 hours (which I agree is
as arbitrary as 2 minutes, 8 minutes, or 1 century) because it introduced
use of DHCPRELEASE message in the agent, which is supported by
Thierry Carrez wrote:
James E. Blair wrote:
Considering that the process used to be
a poll of the ~openstack group on launchpad, it seemed like a fairly
straightforward mapping to ATCs. I wanted to find the easiest way to
get the most people in the community likely to vote as possible
Hi,
I would appreciate if someone replies the email below. Thanks.
Best regards,
Hongbin
On Sun, Jan 25, 2015 at 12:03 AM, Hongbin Lu hongbin...@gmail.com wrote:
Hi Heat team,
I am looking for a solution to bridge between OpenStack and EC2. According
to documents, it seems that Heat has
On Jan 28, 2015, at 9:36 AM, Carl Baldwin c...@ecbaldwin.net wrote:
On Wed, Jan 28, 2015 at 9:52 AM, Salvatore Orlando sorla...@nicira.com
wrote:
The patch Kevin points out increased the lease to 24 hours (which I agree is
as arbitrary as 2 minutes, 8 minutes, or 1 century) because it
Sorry for late reply and thanks for bring this out, I agree the create_db
flag will increase the complexity
so I might do some PoC and write a spec to do it next release
For this sentence, I don't fully understand, are you suggesting to every db
usage remove should be a
patch for a test class?
Hi Dmitry,
I'm not sure if we should user approach when task executor reads
some data from the file system, ideally Nailgun should push
all of the required data to Astute.
But it can be tricky to implement, so I vote for 2nd approach.
Thanks,
On Wed, Jan 28, 2015 at 7:08 PM, Aleksandr Didenko
Thanks JE.
On hosts with multi-core processors, it does not seem optimal to run a
single service instance with just green thread. I understand that on
controller node, we can run one or more nova services but still it does not
seem to utilize multi-core processors.
Is it not a nova scaling
Thank you guys for quick response.
Than, if there is no better option we will follow with second approach.
On Wed, Jan 28, 2015 at 7:08 PM, Evgeniy L e...@mirantis.com wrote:
Hi Dmitry,
I'm not sure if we should user approach when task executor reads
some data from the file system, ideally
If we are going to ignore the IP address changing use-case, can we just
make the default infinity? Then nobody ever has to worry about control
plane outages for existing client. 24 hours is way too long to be useful
anyway.
On Jan 28, 2015 12:44 PM, Salvatore Orlando sorla...@nicira.com wrote:
On Wed, Jan 28, 2015 at 11:56 AM, Sean Dague s...@dague.net wrote:
The following review for Kilo deprecates the EC2 API in Nova -
https://review.openstack.org/#/c/150929/
There are a number of reasons for this. The EC2 API has been slowly
rotting in the Nova tree, never was highly tested,
Also I would like to mention that in plugins user currently can write
'roles': ['controller'],
which means that the task will be applied on 'controller' and
'primary-controller' nodes.
Plugin developer can get this information from astute.yaml file. But I'm
curious if we
should change this
On 1/15/2015 5:43 PM, Steven Hardy wrote:
On Thu, Jan 15, 2015 at 04:49:37PM -0600, Matt Riedemann wrote:
On 1/15/2015 11:40 AM, Matt Riedemann wrote:
On 1/13/2015 9:27 PM, Matt Riedemann wrote:
On 1/13/2015 12:11 PM, Steven Hardy wrote:
On Tue, Jan 13, 2015 at 10:00:04AM -0600, Matt
Hi,
I see there is a blueprint for a Manila driver for CephFS here [1]. It
looks like it was opened back in 2013 but still in Drafting state. Does
anyone know more status about this one?
Thank you,
-Jake
[1] https://blueprints.launchpad.net/manila/+spec/cephfs-driver
On 28 January 2015 at 20:19, Brian Haley brian.ha...@hp.com wrote:
Hi Kevin,
On 01/28/2015 03:50 AM, Kevin Benton wrote:
Hi,
Approximately a year and a half ago, the default DHCP lease time in
Neutron was
increased from 120 seconds to 86400 seconds.[1] This was done with the
goal of
1. as I mentioned above, we should have an interface, and if interface
doesn't
provide required information, you will have to fix it in two places,
in Nailgun and in external-serializers, instead of a single place i.e.
in Nailgun,
another thing if astute.yaml is a bad interface
Excerpts from Johannes Erdfelt's message of 2015-01-28 15:33:25 -0800:
On Wed, Jan 28, 2015, Mike Bayer mba...@redhat.com wrote:
I can envision turning this driver into a total monster, adding
C-speedups where needed but without getting in the way of async
patching, adding new APIs for
On Wed, Jan 28, 2015, Clint Byrum cl...@fewbar.com wrote:
As is often the case with threading, a reason to avoid using it is
that libraries often aren't able or willing to assert thread safety.
That said, one way to fix that, is to fix those libraries that we do
want to use, to be thread
I agree, it is kind of odd to restrict vpn-service to one private tenant
network. Particularly when the current VPN model does allow multiple remote
peer CIDRs to connect to,
neutron ipsec-site-connection-create --name ipsec0 --vpnservice-id vpnsvc0
--ikepolicy-id ike0 --ipsecpolicy-id esp0
Johannes Erdfelt johan...@erdfelt.com wrote:
On Wed, Jan 28, 2015, Mike Bayer mba...@redhat.com wrote:
I can envision turning this driver into a total monster, adding
C-speedups where needed but without getting in the way of async
patching, adding new APIs for explicit async, and everything
You will all, I am sure, be relieved to know that the oslo.vmware release today
was the last library that needed to be released with namespace package changes.
There are a few more patches to land to the requirements list to update the
minimum required version of the oslo libs, and of course
On 01/28/2015 12:51 PM, Kevin Benton wrote:
If we are going to ignore the IP address changing use-case, can we
just make the default infinity? Then nobody ever has to worry about
control plane outages for existing client. 24 hours is way too long to
be useful anyway.
Why would users want
On Wed, Jan 28, 2015, Mike Bayer mba...@redhat.com wrote:
I can envision turning this driver into a total monster, adding
C-speedups where needed but without getting in the way of async
patching, adding new APIs for explicit async, and everything else.
However, I’ve no idea what the developers
+1!
Thanks!
2015-01-29 6:40 GMT+08:00 Steven Dake sd...@redhat.com:
On 01/28/2015 03:27 PM, Adrian Otto wrote:
Magnum Cores,
I propose the following addition to the Magnum Core group[1]:
+ Hongbin Lu (hongbin034)
Please let me know your votes by replying to this message.
Thanks,
On Wed, Jan 28, 2015, at 06:50 PM, Johannes Erdfelt wrote:
On Wed, Jan 28, 2015, Clint Byrum cl...@fewbar.com wrote:
As is often the case with threading, a reason to avoid using it is
that libraries often aren't able or willing to assert thread safety.
That said, one way to fix that,
+1
Will be an interesting analysis; I've also never understood this desire
to use eventlet (perhaps it's written somewhere?). It seems like most of
the applications in openstack (maybe leaving out the WSGI entrypoints)
can be scaled horizontally and mostly just do a large amount of work
that
On Jan 28, 2015, at 4:03 PM, Doug Hellmann d...@doughellmann.com wrote:
On Wed, Jan 28, 2015, at 06:50 PM, Johannes Erdfelt wrote:
On Wed, Jan 28, 2015, Clint Byrum cl...@fewbar.com wrote:
As is often the case with threading, a reason to avoid using it is
that libraries often aren't able
On Wed, Jan 28, 2015, Vishvananda Ishaya vishvana...@gmail.com wrote:
On Jan 28, 2015, at 4:03 PM, Doug Hellmann d...@doughellmann.com wrote:
I hope someone who was around at the time will chime in with more detail
about why green threads were deemed better than regular threads, and I
look
Nik,
I'm sure it requires at least a spec, since there are things that
should be discussed. Who can do it in this release cycle? If there's a
person I'm +1 for refactoring; otherwise - I'd prefer to remove it to
make code more clear.
Thanks,
Igor
On Wed, Jan 28, 2015 at 12:44 PM, Nikolay Markov
Vishvananda Ishaya vishvana...@gmail.com wrote on 01/27/2015 04:29:50 PM:
From: Vishvananda Ishaya vishvana...@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 01/27/2015 04:32 PM
Subject: Re: [openstack-dev] [nova] [api] Get
On 27/01/15 20:36, Angus Salkeld wrote:
Hi all
After having a look at the stats:
http://stackalytics.com/report/contribution/heat-group/90
http://stackalytics.com/?module=heat-groupmetric=person-day
I'd like to propose the following changes to the Heat core team:
Add:
Qiming Teng
Huang
On 01/27/2015 10:51 AM, Doug Hellmann wrote:
The infra team has been working hard to update our Python 3 testing for all
projects to run on 3.4 instead of 3.3. Two of the last projects to be able to
shift are oslo.messaging and oslo.rootwrap. The test suites for both projects
trigger a
Thierry Carrez thie...@openstack.org writes:
Monty Taylor wrote:
You'll notice that I did say in my suggestion that ANYONE should be able
to propose a name - I believe that would include non-dev people. Since
the people in question are marketing people, I would imagine that if any
of them
On Wed, Jan 28, 2015, at 03:23 AM, Denis Makogon wrote:
On Tue, Jan 27, 2015 at 10:26 PM, Gordon Sim g...@redhat.com wrote:
On 01/27/2015 06:31 PM, Doug Hellmann wrote:
On Tue, Jan 27, 2015, at 12:28 PM, Denis Makogon wrote:
I'd like to build tool that would be able to profile
On 2015-01-28 10:29:38 +0100 (+0100), Thierry Carrez wrote:
The proposal as it stands (https://review.openstack.org/#/c/150604/4)
currently excludes all non-ATCs from voting, though. The wider
community was included in previous iterations of the naming process,
so this very much feels like a
Hi folks,
We'll be having the Sahara team meeting in #openstack-meeting-3 channel.
Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meetingiso=20150129T14
--
Sincerely yours,
Sergey Lukjanov
Sahara
Is there a way to overwrite the rule in our hacking (not familiar with
it ...)?
if so ,maybe we can do as suggested to avoid 811 for the class which has
Microversion definition? Thanks
Best Regards!
Kevin (Chen) Ji 纪 晨
Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN
Guys, is it crazy idea to write tests for deployment state on node in
python?
It even can be done in unit tests fashion..
I mean there is no strict dependency on tool from puppet world, what is
needed is access to os and shell, maybe some utils.
What plans have Fuel Nailgun team for testing the
On 01/27/2015 05:41 PM, Michael Still wrote:
Greetings,
I would like to nominate Melanie Witt for the python-novaclient-core team.
(What is python-novaclient-core? Its a new group which will contain
all of nova-core as well as anyone else we think should have core
reviewer powers on just
We need to write tests in way how Puppet community writes. Though if user
uses salt in one stage, it's fine to use tests on python.
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Wed, Jan 28, 2015 at 11:15 PM, Dmitriy Shulyak dshul...@mirantis.com
wrote:
Guys, is it crazy
Welcome Hongbin. +1 from me!
On Wed, Jan 28, 2015 at 2:27 PM, Adrian Otto adrian.o...@rackspace.com wrote:
Magnum Cores,
I propose the following addition to the Magnum Core group[1]:
+ Hongbin Lu (hongbin034)
Please let me know your votes by replying to this message.
Thanks,
Adrian
On 01/28/2015 08:56 PM, Sean Dague wrote:
There is a new stackforge project which is getting some activity now -
https://github.com/stackforge/ec2-api. The intent and hope is that is
the path forward for the portion of the community that wants this
feature, and that efforts will be focused
The pyCADF team is pleased to announce the release of pyCADF 0.7.1. This
release includes several bug fixes as well as many other changes: d59675b Add
new CADF taxonomy types8b82468 Pull out some CADF taxonomy to be
constants84544aa Updated from global requirements For more details, please
Hey list -
As many are aware, we’ve been looking for the one MySQL driver to rule them
all. As has been the case for some weeks now, that driver is PyMySQL, meeting
all the critical requirements we have of: 1. pure python, so eventlet
patchable, 2. Python 3 support 3. Is released on Pypi
Hello Jake,
Main thing, that should be mentioned, is that blueprint has no assignee.
Also, It is created long time ago without any activity after it.
I did not hear any intentions about it, moreover did not see some, at
least, drafts.
So, I guess, it is open for volunteers.
Regards,
Valeriy
Andrew,
What should be sorted out? It is unavoidable that people will comment and
ask questions during development cycle.
I am not sure that merging spec as early as possible, and than add comments
and different fixes is good strategy.
On the other hand we need to eliminate risks.. but how merging
On Wed, Jan 28, 2015 at 3:06 AM, Evgeniy L e...@mirantis.com wrote:
Hi,
+1 for having primary-controller role in terms of deployment.
Yes, we need to continue to be able to differentiate the difference
between the first node in a set of roles, and all the others.
For controllers we have logic
Mike Bayer mba...@redhat.com wrote:
Hey list -
As many are aware, we’ve been looking for the one MySQL driver to rule them
all. As has been the case for some weeks now, that driver is PyMySQL,
meeting all the critical requirements we have of: 1. pure python, so
eventlet patchable,
Some follow up questions on this.
In the specs, i see that during a create_port, there's provisions to query
the external source by Pluggable IPAM to return the IP.This works fine for
cases where the external source (say, DHCP server) can be queried for the IP
address when a launch happens.
Hi, Daniel
I recently tried the libvirt.cpu_mode and libvirt.cpu_model when I was
working on cpu_info related code and found bug
https://bugs.launchpad.net/nova/+bug/1412994 . The reason is because with
these two flags, all guests launched on the host will use them, while when host
Magnum Cores,
I propose the following addition to the Magnum Core group[1]:
+ Hongbin Lu (hongbin034)
Please let me know your votes by replying to this message.
Thanks,
Adrian
[1] https://review.openstack.org/#/admin/groups/473,members Current Members
On 01/28/2015 03:27 PM, Adrian Otto wrote:
Magnum Cores,
I propose the following addition to the Magnum Core group[1]:
+ Hongbin Lu (hongbin034)
Please let me know your votes by replying to this message.
Thanks,
Adrian
+1
Regards
-steve
[1]
Thanks the team for the trust. It's my pleasure to work with you.
Regards,
Qiming
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
I'm short on time so I apologize for my candor since I need to get straight
to the point.
I love reading the various opinions and my team is immensely excited with
OpenStack is maturing. But this is lunacy.
I looked at the patch being worked [1] to change how things are done and
have more
1 - 100 of 150 matches
Mail list logo
