Hello.
On Thu, Jan 23, 2014 at 6:47 AM, ZhiQiang Fan wrote:
>
> I noticed that in openstack-dev/hacking project, there is very little test
> code, is there any particular reason why it is in such situation?
>
Yes, there is. Every rule have a docstring that not only provides examples
of good and
Dear stackers,
We inspected the Horizon (Havana release) for web accessibility and
found the following problems, as it's required by our domestic standards.
1.1.1 Non-text Contents
- A few non-text contents such as Network Topology (for Neutron) and
Resource Usage (for Ceilometer) have no text
Hello.
On Thu, Jan 23, 2014 at 8:06 AM, Steve Martinelli wrote:
> #3 - I'll leave this to others
>
> [image: Inactive hide details for Mario Adessi ---01/22/2014 09:37:48
> PM---I'd like to begin contributing to the keystone project. Keys]Mario
> Adessi ---01/22/2014 09:37:48 PM---I'd like to beg
For the ceilometer part, it seems have overlap, but I am not sure about Nova
part. IIUC, Nova doesn't collect power/temperature for now.
Thanks
--fengqian
-Original Message-
From: Tim Bell [mailto:tim.b...@cern.ch]
Sent: Thursday, January 23, 2014 2:21 PM
To: OpenStack Development Maili
Is there overlap with https://launchpad.net/kwapi and
https://blueprints.launchpad.net/ironic/+spec/send-data-to-ceilometer ?
Tim
From: Gao, Fengqian [mailto:fengqian@intel.com]
Sent: 23 January 2014 06:25
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Nova] Power/temperatu
Hello everyone,
The Barbican team is proud to announce the second milestone delivery for the
OpenStack Icehouse series.
Information on the milestone and its associated tarball are available at:
https://launchpad.net/barbican/icehouse/icehouse-2
With this milestone, 3 blueprints have been imple
Hi, all,
I would like to propose adding power/temperature monitors in Nova for the
scheduler. I builded a wiki to record the design notes,
https://wiki.openstack.org/wiki/User_talk:Fengqian#Why_and_how_to_use_Intel_Node_Manager_in_Openstack
Please help to review the following patches if you are i
Hi,
Is it possible to enable the hugepages in the guest OS for the VMs launched in
OpenStack (with KVM hypervisor)? Specifically is it possible to pass the
"-mem-path" option when invoking QEMU?
Thanks,
Anil
___
OpenStack-dev mailing list
OpenStack-d
Any possibility we can nail the keywords in the next 12 - 24 hrs? So we can
decide the scope in Icehouse release and then, discuss who can do what?
Shixiong
On Jan 22, 2014, at 11:20 AM, Collins, Sean
wrote:
> I don't know if it's reasonable to expect a deployment of OpenStack that
> has an
you can split H306 to several patches since it contains so much files.
optional: It would be really nice if you can fix the unused import problem
(if exist) in the same time, this seems can be checked via IDE
On Wed, Jan 22, 2014 at 7:23 PM, Pavlo Shchelokovskyy <
pshchelokovs...@mirantis.com>
On 22/01/14 06:23, Pavlo Shchelokovskyy wrote:
Hi all,
we have an approved blueprint that concerns reducing number of ignored
PEP8 and openstack/hacking style checks for heat
(https://blueprints.launchpad.net/heat/+spec/reduce-flake8-ignored-rules).
I've been already warned that enabling some of
Hey Mario,
Welcome and thanks for helping out!
The developer docs are a great place to get started.
#1 - Not sure if there is anything recent, but here is an old diagram:
http://ilearnstack.files.wordpress.com/2013/04/keystone.png
#2 - I would read up on the section (Running with PDB)
http://do
> -Original Message-
> From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]
> Sent: Wednesday, January 22, 2014 2:26 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Cc: Jinbo (Justin)
> Subject: Re: [openstack-dev] question of vcpu-memory-hotplug progress
> > The
Hi,
I noticed that in openstack-dev/hacking project, there is very little test
code, is there any particular reason why it is in such situation?
since hacking module is depended by almost all openstack projects, I think
hacking code should be tested well at least
for i.e. the hacking rule h233 i
I'd like to begin contributing to the keystone project.
Keystone, along with all the other major infrastructure components in
OpenStack, is a rather large project. I've read over the developer
documentation, but was hoping to get help with some questions.
(1) Are there diagrams that describe how
Fernando,
As you are making changes to Fuel, it's important to keep the following
considerations in mind:
- 3.2.x doesn't have PuppetDB
- 4.x doesn't have Puppet Master at all
Dev team deliberately switched to masterless puppet just recently, due to
the scaling issues as well as a number of rando
Hi All,
During tempest sprint in Montreal, as we were writing API tests, we noticed
a behavior which we believed is an issue with the Neutron API (or perhaps
documentation or both)
Let me start with a question:
If one executes an api to create/delete/update a neutron resource, what is
the API's
+1 yes that is true.
Thanks,
Craig
On Wed, Jan 22, 2014 at 4:52 PM, Kaleb Pomeroy
wrote:
> I think that may have been a slight oversite. We will likely have the
> following two routes
>
> /datastores//configuration/ would be the collection of all
> parameters
> /datastores//configuration/:para
Gordon Chung wrote on 2014-01-21:
>> If the resources defined in the pipeline doesn't match any resource
>> file loader, it will be treated as directly passing to the pollsters. E.g.
>> resources:
>> - fileloader:///foo/bar
>> - snmp://2.2.2.2
>> The endpoint 'snmp://2.2.2.2' wi
On Wed, 2014-01-22 at 17:59 -0500, Sean Dague wrote:
> On 01/22/2014 05:52 PM, Clint Byrum wrote:
> > Excerpts from Jay Pipes's message of 2014-01-22 13:43:41 -0800:
> >> On Wed, 2014-01-22 at 15:39 -0500, Sean Dague wrote:
> >>>
> >>> ==
> >>> Executive Summary
> >>> =
So, a conversation came again up today around whether or not Ironic will,
in the future, support operations on groups of nodes. Some folks have
expressed a desire for Ironic to expose operations on groups of nodes;
others want Ironic to host the hardware-grouping data so that eg. Heat and
Tuskar ca
Robert Collins writes:
> On 23 January 2014 09:39, Sean Dague wrote:
>>
>> Changes coming in gate structure
>>
>
>> Svelt Gate
>> ==
>>
>> The gate jobs will be trimmed down immensely. Nothing project
>> specific, so pep8
Hi all,
The [state-management] project team holds a weekly meeting in
#openstack-meeting on thursdays, 2000 UTC. The next meeting is tommorow,
2014-01-23!!!
As usual, everyone is welcome :-)
Link: https://wiki.openstack.org/wiki/Meetings/StateManagement
Taskflow: https://wiki.openstack.org
James Slagle wrote:
> I read through that wiki page. I did have a couple of questions:
>
> Who usually runs through the steps there? You? or a project member?
Me for integrated projects (and most incubated ones). A project member
for everything else.
> When repo_tarball_diff.sh is run, are there
On 23 January 2014 09:39, Sean Dague wrote:
>
> Changes coming in gate structure
>
> Svelt Gate
> ==
>
> The gate jobs will be trimmed down immensely. Nothing project
> specific, so pep8 / unit tests all ripped out, no func
On 01/22/2014 05:52 PM, Clint Byrum wrote:
> Excerpts from Jay Pipes's message of 2014-01-22 13:43:41 -0800:
>> On Wed, 2014-01-22 at 15:39 -0500, Sean Dague wrote:
>>>
>>> ==
>>> Executive Summary
>>> ==
>>> To summarize, the effects of these change
Excerpts from Jay Pipes's message of 2014-01-22 13:43:41 -0800:
> On Wed, 2014-01-22 at 15:39 -0500, Sean Dague wrote:
> >
> > ==
> > Executive Summary
> > ==
> > To summarize, the effects of these changes will be:
> >
> > - 1) Decrease the impact
I think that may have been a slight oversite. We will likely have the following
two routes
/datastores//configuration/ would be the collection of all parameters
/datastores//configuration/:parameter would be an individual setting.
- kpom
From: Craig Vyvial [cp16
I agree, the gantt tree during the interim will be tightly coupled with the
nova tree, any changes to those internal nova APIs will have to be reflected
back into the gantt tree. Ultimately we want to completely decouple gantt from
nova but that is a harder problem than just moving the schedule
On 01/22/2014 05:24 PM, Peter Portante wrote:
> Can you consider issuing the check job before forwarding to the gate if
> the current patch set is not already (re)based against master? That
> way, if it is, and there was a successful check job, even if it was days
> old, a new one would not be nee
On 01/22/2014 04:43 PM, Jay Pipes wrote:
> On Wed, 2014-01-22 at 15:39 -0500, Sean Dague wrote:
>>
>> ==
>> Executive Summary
>> ==
>> To summarize, the effects of these changes will be:
>>
>> - 1) Decrease the impact of failures resetting the entir
2014/1/22 Joe Gordon
>
>
>
> On Tue, Jan 21, 2014 at 7:35 PM, Dugger, Donald D <
> donald.d.dug...@intel.com> wrote:
>
>> Well, the first goal is to get the scheduler code into a separate tree,
>> even though that code is still utilizing common code from nova. Right now
>> just about every sched
Can you consider issuing the check job before forwarding to the gate if the
current patch set is not already (re)based against master? That way, if it
is, and there was a successful check job, even if it was days old, a new
one would not be needed? Perhaps?
On 01/22/2014 04:43 PM, Jay Pipes wrote:
> On Wed, 2014-01-22 at 15:39 -0500, Sean Dague wrote:
>>
>> ==
>> Executive Summary
>> ==
>> To summarize, the effects of these changes will be:
>>
>> - 1) Decrease the impact of failures resetting the entir
Ok with overwhelming support for #3.
What if we modified #3 slightly because looking at it again seems like we
could shorten the path since /datastores//configuration doesnt
do anything.
instead of
#1
/datastores//configuration/parameters
maybe:
#2
/datastores//parameters
#3
/datastores//configu
Hi
On 22 January 2014 21:33, Fox, Kevin M wrote:
> I think we're pretty far off in a tangent though. My main point was, if
> you can't selectively restart services as needed, I'm not sure how useful
> patching the image really is over a full reboot. It should take on the same
> order of magnitud
On 01/21/2014 04:43 PM, Joe Gordon wrote:
>
>
>
> On Thu, Jan 16, 2014 at 4:42 PM, Dugger, Donald D
> mailto:donald.d.dug...@intel.com>> wrote:
>
> OK, it looks like the concensus is that we don't try and keep the
> gantt tree in sync with nova instead we:
>
> 1) Get the current g
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tommorrow Thursday, January 23rd at 22:00 UTC in the #openstack-meeting
channel.
The agenda for tommorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add an item
On 22/01/14 12:21 +, Steven Hardy wrote:
On Wed, Jan 22, 2014 at 01:23:05PM +0200, Pavlo Shchelokovskyy wrote:
Hi all,
we have an approved blueprint that concerns reducing number of ignored PEP8
and openstack/hacking style checks for heat (
https://blueprints.launchpad.net/heat/+spec/reduce
On Wed, Jan 22, 2014 at 5:19 AM, Julien Danjou wrote:
> On Tue, Jan 21 2014, Joe Gordon wrote:
>
> > I would like to propose having a integration test job in Oslo incubator
> > that syncs in the code, similar to how we do global requirements.
>
> I don't think that would be possible as a voting j
Hi Matthieu,
Am 22.01.14 20:02, schrieb Matthieu Huin:
> The idea is to have a middleware checking a domain's current usage
> against a limit set in the configuration before allowing an upload.
> The domain id can be extracted from the token, then used to query
> keystone for a list of projects be
On Wed, Jan 22, 2014 at 3:22 AM, Flavio Percoco wrote:
> On 21/01/14 13:14 -0500, Joe Gordon wrote:
>
>>
>> On Jan 17, 2014 12:24 AM, "Flavio Percoco" wrote:
>>
>>>
>>> On 16/01/14 17:32 -0500, Doug Hellmann wrote:
>>>
On Thu, Jan 16, 2014 at 3:19 PM, Ben Nemec
wrote:
On Wed, 2014-01-22 at 15:39 -0500, Sean Dague wrote:
>
> ==
> Executive Summary
> ==
> To summarize, the effects of these changes will be:
>
> - 1) Decrease the impact of failures resetting the entire gate queue
>by doing the heavy testing in t
Maybe I misunderstand, but I thought:
kexec - lets you boot a new kernel/initrd starting at the point a boot loader
would skipping the bios init. All previous running processes are not running in
the new boot just like a normal reboot.
CRIU - Lets you snapshot/restart running processes.
While
On Tue, Jan 21, 2014 at 7:35 PM, Dugger, Donald D wrote:
> Well, the first goal is to get the scheduler code into a separate tree,
> even though that code is still utilizing common code from nova. Right now
> just about every scheduler file includes some nova modules. Ultimately
> yes, we want
Another +1 for option 3.
Greg
On Jan 22, 2014, at 2:27 PM, Denis Makogon
mailto:dmako...@mirantis.com>> wrote:
Goodday to all.
#3 looks more than acceptable.
/datastores//configuration/parameters.
According to configuration parameters design, a configuration set must be
associated to exactly
Excerpts from Keith Basil's message of 2014-01-22 12:27:50 -0800:
> On Jan 22, 2014, at 1:53 PM, Jay Pipes wrote:
>
> > On Wed, 2014-01-22 at 13:15 -0500, Dan Prince wrote:
> >>
> >> - Original Message -
> >>> From: "Clint Byrum"
> >>> To: "openstack-dev"
> >>> Sent: Wednesday, January
On Wed, Jan 22, 2014 at 1:39 PM, Sean Dague wrote:
>
> Changes coming in gate structure
>
>
> Unless you've been living under a rock, on the moon, around Saturn,
> you'll have noticed that the gate has been quite backed up the last
On Wed, 2014-01-22 at 12:12 -0800, Clint Byrum wrote:
> Excerpts from Jay Pipes's message of 2014-01-22 10:53:14 -0800:
> > On Wed, 2014-01-22 at 13:15 -0500, Dan Prince wrote:
> > >
> > > - Original Message -
> > > > From: "Clint Byrum"
> > > > To: "openstack-dev"
> > > > Sent: Wednesda
Changes coming in gate structure
Unless you've been living under a rock, on the moon, around Saturn,
you'll have noticed that the gate has been quite backed up the last 2
weeks. Every time we get towards a milestone this gets measur
On 01/22/2014 03:19 PM, Jay Pipes wrote:
On Tue, 2014-01-21 at 01:15 -0500, Yair Fried wrote:
I seem to be unable to convey my point using generalization, so I will give a
specific example:
I would like to have "update dns server" as an additional network scenario.
Currently I could add it to
On Thu, Jan 23, 2014 at 12:04 AM, CARVER, PAUL wrote:
>
> Can you elaborate on what you mean by this? You can turn of Neutron’s
> dnsmasq on a per network basis, correct? Do you mean something else by
> “make its dnsmasq service quiet”?
>
What I meant is for dnsmasq to not send offers to specifi
Excerpts from Fox, Kevin M's message of 2014-01-22 12:19:56 -0800:
> I think most of the time taken to reboot is spent in bringing down/up the
> services though, so I'm not sure what it really buys you if you do it all. It
> may let you skip the crazy long bootup time on "enterprise" hardware, bu
On Jan 22, 2014, at 1:53 PM, Jay Pipes wrote:
> On Wed, 2014-01-22 at 13:15 -0500, Dan Prince wrote:
>>
>> - Original Message -
>>> From: "Clint Byrum"
>>> To: "openstack-dev"
>>> Sent: Wednesday, January 22, 2014 12:45:45 PM
>>> Subject: Re: [openstack-dev] [TripleO] our update story:
Goodday to all.
#3 looks more than acceptable.
/datastores//configuration/parameters.
According to configuration parameters design, a configuration set must be
associated to exactly one datastore.
Best regards, Denis Makogon.
2014/1/22 Michael Basnight
> On Jan 22, 2014, at 10:19 AM, Kaleb Po
On Tue, 2014-01-21 at 01:15 -0500, Yair Fried wrote:
> I seem to be unable to convey my point using generalization, so I will give a
> specific example:
> I would like to have "update dns server" as an additional network scenario.
> Currently I could add it to the existing module:
>
> 1. tests c
I think most of the time taken to reboot is spent in bringing down/up the
services though, so I'm not sure what it really buys you if you do it all. It
may let you skip the crazy long bootup time on "enterprise" hardware, but that
could be worked around with kexec on the full reboot method too.
Excerpts from Jay Pipes's message of 2014-01-22 10:53:14 -0800:
> On Wed, 2014-01-22 at 13:15 -0500, Dan Prince wrote:
> >
> > - Original Message -
> > > From: "Clint Byrum"
> > > To: "openstack-dev"
> > > Sent: Wednesday, January 22, 2014 12:45:45 PM
> > > Subject: Re: [openstack-dev] [
Hi All,
Are we using tools/install_venv_common.py in python-troveclient,
If so just let us know.
Otherwise, it may be cleaned up (removing it from openstack-common.conf)
Thanks.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http:
On Thu, Jan 16, 2014 at 10:32 AM, Thierry Carrez wrote:
> James Slagle wrote:
>> [...]
>> And yes, I'm volunteering to do the work to support the above, and the
>> release work :).
>
> Let me know if you have any question or need help. The process and tools
> used for the integrated release are de
Hi folks,
At this point we have a few major action items, mostly patches on review.
Please note that the gate is in pretty bad shape, so don't expect anything
to be approved/merged until this is sorted out.
1) SSL extension
https://review.openstack.org/#/c/63510/
The code here is in a good shape
On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote:
> My thoughts so far:
>
> /datastores//configuration/parameters (Option Three)
> + configuration set without an associated datastore is meaningless
> + a configuration set must be associated to exactly one datastore
> + each datastore must have
Yuriy Taraday wrote:
>Fuel needs to manage nodes directly via DHCP and PXE and you can't do that
>with Neutron since you can't make its >dnsmasq service quiet.
Can you elaborate on what you mean by this? You can turn of Neutron’s dnsmasq
on a per network basis, correct? Do you mean something el
Hello.
On Tue, Jan 21, 2014 at 12:52 PM, Dong Liu wrote:
> What's your opinion?
>
We've just discussed a use case for this today. I want to create a sandbox
for Fuel but I can't do it with OpenStack.
The reason is a bit different from telecom case: Fuel needs to manage nodes
directly via DHCP a
Hi
Looks good approach. Lets start discussion.
I propose API spec for it
https://gist.github.com/andreyshestakov/8559309
Please look it and add your advices and comments.
Thanks
On Thu, Nov 21, 2013 at 2:44 AM, McReynolds, Auston
wrote:
> With "Multiple Datastore Types/Versions" merged to mas
Agreed. That would be a good place for that check.
Carl
On Wed, Jan 22, 2014 at 6:40 AM, Paul Ward wrote:
> Thanks for your input, Carl. You're right, it seems the more appropriate
> place for this is _validate_subnet(). It checks ip version, gateway, etc...
> but not the size of the subnet.
Greetings,
I'd be interested in some opinions and feedback on the following blueprint:
https://blueprints.launchpad.net/ceilometer/+spec/quotas-on-alarms
I think it'd be interesting to allow admins to limit the number of running
alarms at any of the three levels defined by keystone. Thoughts ?
That is correct, Xu Han!
> On Jan 22, 2014, at 11:14 AM, "Xuhan Peng" wrote:
>
> Ian,
>
> I think the last "two attributes" PDF from Shixiong's last email is trying to
> solve the problem you are saying, right?
> —
> Xu Han Peng (xuhanp)
>
>
>> On Wed, Jan 22, 2014 at 8:15 PM, Ian Wells
Sean, I agree with you. I prefer OpenStack as the single source of truth. What
end user chooses may be different. But with this pair of keywords, at least we
provide comprehensive coverage on all scenarios.
For Icehouse, I suggest we only consider the supports for the scenarios that
OpenStack h
Greetings,
I'd be interested in your opinions and feedback on the following blueprint:
https://blueprints.launchpad.net/swift/+spec/domain-level-quotas
The idea is to have a middleware checking a domain's current usage against a
limit set in the configuration before allowing an upload. The doma
Agreed, it is tricky if we try to only restart what we've changed.
OR, just restart everything. We can make endpoints HA and use rolling
updates to avoid spurious faults.
There are complex ways to handle things even smoother.. but I go back to
"What does complexity cost?"
Excerpts from Fox, Kevi
On Wed, 2014-01-22 at 13:15 -0500, Dan Prince wrote:
>
> - Original Message -
> > From: "Clint Byrum"
> > To: "openstack-dev"
> > Sent: Wednesday, January 22, 2014 12:45:45 PM
> > Subject: Re: [openstack-dev] [TripleO] our update story: can people live
> > with it?
> >
> > Excerpts
- Original Message -
> Oh dear user... :)
>
> I'll step a little bit back. We need to agree if we want to name
> concepts one way in the background and other way in the UI for user (did
> we already agree on this point?). We all know pros and cons. And I will
> still fight for users to g
Excerpts from Dan Prince's message of 2014-01-22 10:15:20 -0800:
>
> - Original Message -
> > From: "Clint Byrum"
> > To: "openstack-dev"
> > Sent: Wednesday, January 22, 2014 12:45:45 PM
> > Subject: Re: [openstack-dev] [TripleO] our update story: can people live
> > with it?
> >
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/2014 09:38 AM, Sean Dague wrote:
> Thanks to everyone that's been pitching in digging on reset bugs.
> More help is needed. Many core reviewers are at this point
> completely ignoring normal reviews until the gate is back, so if
> you are wait
Clint wrote:
> I would call your e-mail a documentation/roadmap bug. This plan may
> have been recorded somewhere, but for me it has just always been in my
> head as the end goal (thanks to Robert Collins for drilling the hole
> and pouring it in there btw ;).
I found the following links helpful i
On 01/22/2014 12:17 PM, Dan Prince wrote:
> I've been thinking a bit more about how TripleO updates are developing
> specifically with regards to compute nodes. What is commonly called the
> "update story" I think.
>
> As I understand it we expect people to actually have to reboot a compute node
Another tricky bit left is how to handle service restarts as needed?
Thanks,
Kevin
From: Dan Prince [dpri...@redhat.com]
Sent: Wednesday, January 22, 2014 10:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev]
Hi everyone,
A milestone-proposed branch was created for Swift in preparation for the
1.12.0 release.
Please test the proposed delivery to ensure no critical regression found
its way in. Release-critical fixes might be backported to the
milestone-proposed branch until final release, and will be t
Hi everyone,
Milestone-proposed branches were created for Keystone, Glance, Nova,
Neutron, Cinder, Ceilometer, Heat and and Trove in preparation
for the icehouse-2 milestone publication tomorrow.
Horizon should be there in a few hours.
You can find candidate tarballs at:
http://tarballs.openstac
My thoughts so far:
/datastores//configuration/parameters (Option Three)
+ configuration set without an associated datastore is meaningless
+ a configuration set must be associated to exactly one datastore
+ each datastore must have 0-1 configuration set
+ All above relationships are immediately a
- Original Message -
> From: "Clint Byrum"
> To: "openstack-dev"
> Sent: Wednesday, January 22, 2014 12:45:45 PM
> Subject: Re: [openstack-dev] [TripleO] our update story: can people live
> with it?
>
> Excerpts from Dan Prince's message of 2014-01-22 09:17:24 -0800:
> > I've bee
Excerpts from Dan Prince's message of 2014-01-22 09:17:24 -0800:
> I've been thinking a bit more about how TripleO updates are developing
> specifically with regards to compute nodes. What is commonly called the
> "update story" I think.
>
> As I understand it we expect people to actually have to
Hi,
Though cpu/disk/ram stats are overcommitted in openstack, hypervisor summary
page in horizon UI displays the actual stats on compute node instead of
overcommitted values calculated in openstack. This gives incorrect data to the
user while provisioning instances as the used value of cpu/disk
On 22/01/14 10:59 -0600, Ben Nemec wrote:
On 2014-01-22 06:32, Sean Dague wrote:
I think we need to graduate things to stable interfaces a lot faster.
Realizing that stable just means "have to deprecate to change it". So
the interface is still changeable, just requires standard deprecation
techn
On 2014-01-22 06:32, Sean Dague wrote:
I think we need to graduate things to stable interfaces a lot faster.
Realizing that stable just means "have to deprecate to change it". So
the interface is still changeable, just requires standard deprecation
techniques. Which we are trying to get more pyth
I've been thinking a bit more about how TripleO updates are developing
specifically with regards to compute nodes. What is commonly called the "update
story" I think.
As I understand it we expect people to actually have to reboot a compute node
in the cluster in order to deploy an update. This
I like #4 over #5 because it seems weird to have to create a configuration
first to see what parameters are allowed. With #4 you could look up what is
allowed first then create your configuration.
Robert
On Jan 22, 2014 10:18 AM, "Craig Vyvial" wrote:
> Hey everyone I have run into an issue with
Thanks for spotting that one Mark! Good catch!
I've put together a quick test case and patch for this.
https://review.openstack.org/#/c/68420
Thanks again.
Tom
On Tue, Jan 21, 2014 at 10:48:40PM -0800, Mark Washenberger wrote:
> I found the cause. When using role-based protections, instead of st
On 01/22/2014 03:01 AM, Robert Collins wrote:
I certainly think having the MTU set to the right value is important.
I wonder if there's a standard way we can signal the MTU (e.g. in the
virtio interface) other than DHCP. Not because DHCP is bad, but
because that would work with statically injecte
On Wed, Jan 22, 2014 at 1:05 AM, Public Mail wrote:
> Hi All,
>
> I have two questions ...
>
> 1) Glance v1 APIs can take a --location argument when creating an image
>but v2 APIs can't - bug or feature? (Details below)
>
I'd call that a missing feature. I think we probably need
Thanks for the update!
One question - is it possible to move the "Deploying Status" bar from page 12
to page 14?
The reason is that the former looks like a "Deployment Creation" page, while
the latter is
a "Deployment Detail" page. For me, the former is about sending parameters to
the API to
I don't know if it's reasonable to expect a deployment of OpenStack that
has an *external* DHCP server. It's certainly hard to imagine how you'd
get the Neutron API and an external DHCP server to agree on an IP
assignment, since OpenStack expects to be the source of truth.
--
Sean M. Collins
Ian,
I think the last "two attributes" PDF from Shixiong's last email is trying to
solve the problem you are saying, right?
—
Xu Han Peng (xuhanp)
On Wed, Jan 22, 2014 at 8:15 PM, Ian Wells wrote:
> On 21 January 2014 22:46, Veiga, Anthony
> wrote:
>>
>>Hi, Sean and Xuhan:
>>
>> I tota
On Jan 20, 2014, at 3:02 AM, Jaromir Coufal wrote:
> Hello everybody,
>
> based on feedback which I received last week, I am sending updated
> wireframes. They are still not completely final, more use-cases and smaller
> updates will occur, but I believe that we are going forward pretty well.
Hey everyone I have run into an issue with the configuration parameter URI.
I'd like some input on what the URI might look like for getting the list
configuration parameters for a specific datastore.
Problem: Configuration parameters need to be selected per datastore.
Currently: Its setup to use
On Jan 22, 2014, at 10:53 AM, Jaromir Coufal wrote:
> Oh dear user... :)
>
> I'll step a little bit back. We need to agree if we want to name concepts one
> way in the background and other way in the UI for user (did we already agree
> on this point?). We all know pros and cons. And I will st
Hey everybody,
I am sending updated wireframes.
http://people.redhat.com/~jcoufal/openstack/tripleo/2014-01-22_tripleo-ui-icehouse.pdf
Updates:
* p15-18 for down-scaling deployment
Any questions are welcome, I am happy to answer them.
-- Jarda
On 2014/16/01 01:50, Jaromir Coufal wrote:
Hi f
Oh dear user... :)
I'll step a little bit back. We need to agree if we want to name
concepts one way in the background and other way in the UI for user (did
we already agree on this point?). We all know pros and cons. And I will
still fight for users to get global infrastructure terminology (
> On Jan 22, 2014, at 4:02 AM, Jaromir Coufal wrote:
>
> >
> >
> > On 2014/22/01 00:56, Tzu-Mainn Chen wrote:
> >> Hiya - Resource is actually a Heat term that corresponds to what we're
> >> deploying within
> >> the Overcloud Stack - i.e., if we specify that we want an Overcloud with 1
> >> Co
1 - 100 of 141 matches
Mail list logo
