Just to ensure that everyone knows - patch is merged. I hope that we will
see performance improvements, and looking for test results :)
On Thu, Jul 23, 2015 at 1:13 PM Aleksandr Didenko adide...@mirantis.com
wrote:
Hi,
guys, we're about to switch keystone to apache wsgi by merging [0]. Just
On Fri, Jul 24, 2015 at 12:02 AM, Mohammad Banikazemi m...@us.ibm.com wrote:
Daneyon Hansen (danehans) daneh...@cisco.com wrote on 07/23/2015
03:40:38 PM:
From: Daneyon Hansen (danehans) daneh...@cisco.com
To: OpenStack Development Mailing List (not for usage questions)
+1
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Thu, Jul 23, 2015 at 11:48 AM, Mike Scherbakov mscherba...@mirantis.com
wrote:
+1
On Thu, Jul 23, 2015 at 10:50 AM Evgeniy L e...@mirantis.com wrote:
+1
On Thu, Jul 23, 2015 at 6:14 PM, Dmitry Pyzhov
+1
2015-07-24 1:56 GMT+03:00 Sergey Vasilenko svasile...@mirantis.com:
+1
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
Hi Chandeep, There are no fees. It would be great if you could join us. Also,
please feel free to add to the agenda topics that you would like to cover.
If you are traveling, I can advise on hotels.
Regards --Roland
From: Chandeep Khamba ckha...@cray.commailto:ckha...@cray.com
Reply-To:
Since we are in FF state already, I'd like to have urgent estimate from one
of fuel-library cores:
- holser
- alex_didenko
- aglarendil
- bogdando
aglarendil is on vacation though. Guys, please take a look at
https://review.openstack.org/#/c/196114/ - can we accept it as exception?
Seems to be
Hi Roland,
I am still a newbie to Monasca , but would like to hear and participate
in the agenda items we already have.
If I have something specific would definitely add it.
Thanks
On 7/23/15, 1:58 PM, Hochmuth, Roland M roland.hochm...@hp.com wrote:
Hi Chandeep, There are no fees. It would
On Wed, Jul 22, 2015 at 6:32 AM Fedor Zhadaev fzhad...@mirantis.com wrote:
Thanks for your answers.
Let me clarify some points:
Sure, we have to validate hostnames during node renaming. And sure we do
it. This issue appears when we already have node with name 'node-X' and new
node is
Hi,
Is the schedule for this meetup confirmed .
https://etherpad.openstack.org/p/monasca_liberty_mid_cycle
I would like to know if there is any fees involved to join in , or I could just
come in .
Thanks
CHandeep
__
On Thu, Jul 23, 2015 at 1:45 PM, Kevin Benton blak...@gmail.com wrote:
We ran in to this long ago.
What are some other examples? We've be good about keeping the network L2
only. Segments, VLAN transparency, and other properties of the network are
all L2.
Another thing is that we create
Hi Simon, Sorry, we don't have any information on our Wiki. Ceilosca leverages
the Ceilometer data collection pipeline via a Ceilometer-Monasca Publisher and
the Ceilometer API via a Ceilometer-Monasca Storage Driver and is completely
compatible with the Ceilometer v2 API.
Regards --Roland
+1
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Thu, Jul 23, 2015 at 2:40 AM, Derek Higgins der...@redhat.com wrote:
See below
On 21/07/15 20:29, Derek Higgins wrote:
Hi All,
Something we discussed at the summit was to switch the focus of
tripleo's deployment method to deploy using instack using images built
with
Hi,
guys, we're about to switch keystone to apache wsgi by merging [0]. Just
wanted to make sure everyone is aware of this change.
If you have any questions or concerns let's discuss them in this thread.
Regards,
Alex
[0] https://review.openstack.org/#/c/204111/
Hello Vladimir, from me -1.
We can discuss if enable fuelmenu=yes or not in grub, but I wouldn't get
rid of it. I've never heard complaints against fuelmenu from users, and
it's widely used for basic settings afterinstall.
If the users had to manually edit another configuration file, should
I've released mock 1.3 which really correctly fixes the behaviour of
mock_open. Unfortunately there is a test in nova that is faulty (and
was faulty but silently so with 1.2).
https://review.openstack.org/204222 fixes this up.
I had intended to let it land before releasing, but I forgot I had
On 07/23/2015 06:34 PM, Robert Collins wrote:
I've released mock 1.3 which really correctly fixes the behaviour of
mock_open. Unfortunately there is a test in nova that is faulty (and
was faulty but silently so with 1.2).
https://review.openstack.org/204222 fixes this up.
I had intended
Roland,
Could you please specify the time of the meetup , I need to book my
Airtickes accordingly
On 7/23/15, 4:30 PM, Chandeep Khamba ckha...@cray.com wrote:
Hi Roland,
I am still a newbie to Monasca , but would like to hear and participate
in the agenda items we already have.
If I have
IOW, I don't think what I
proposed in adding L3 stuff to the network that wasn't already here.
The point I'm trying to make is that there isn't any L3 stuff on the
network itself. There are L3 things that depend on the network because an
L2 network carries them. But the routed network proposes
Angus,
yes, oslo.serialization should remain suitable for security-sensitive
purposes. i don't believe we use either of the features today and no
intention to add it the future.
-- dims
On Thu, Jul 23, 2015 at 12:56 AM, Angus Lees g...@inodes.org wrote:
I'm working on a draft spec[1] for a new
We had that before and had very poor validation. Removing fuelmenu
would make the experience quite manual and prone to errors.
This topic comes up once a year only from Fuel Python developers
because they rarely use it and no dev cycles have been invested in
improving it.
The actual Fuel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
I've stumbled on this one. It turns out we gate neutron against
openstack installation that runs vpn-agent instead of l3-agent [1]. Is
it really what we want to do? I would expect that gate validates l3
agent as is, as is usually found on
Hello,
Here's my 2 cents on it.
I think the effort we put to support fuelmenu doesn't worth it. I used
to deploy fuel too often in previous release, and I never used
features of fuelmenu? Why? Because I prefer to apply changes on
already deployed node. Moreover, I don't like that users are
Jim,
I'm redirecting your question to oslo folks, as I'm afraid my answer can
be wrong.
On 07/23/2015 01:55 PM, Jim Rollenhagen wrote:
On Wed, Jul 22, 2015 at 02:40:47PM +0200, Dmitry Tantsur wrote:
Hi all!
Currently _spawn_worker in the conductor manager raises
NoFreeConductorWorker if
This is just a reminder that the Manila midcycle meetup is next week
(July 29-30). Please add your name to the etherpad if you intend to
join! If you have a topic to discuss it's not too late to suggest it.
https://etherpad.openstack.org/p/manila-liberty-midcycle-meetup
-Ben Swartzlander
How much effort are we spending? I'm not so sure it's a major development drain.
Since Fuel 6.0 dev cycle (Sept 2014) until now there have been 34
commits into Fuelmenu:
* New features/functionality: 12
* Bugfix: 15
* Other: 7 (version bumps, and commits without bug ID)
Across 3 releases, that's
It's a remnant of pre-*aaS split times - We have to reexamine our
testing strategy post-split.
- Original Message -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
I've stumbled on this one. It turns out we gate neutron against
openstack installation that runs vpn-agent
Hi Yingxin,
+1 to joining the sprint. If you can't make the mid-cycle sprint in
person, we're planning to have a remote option. Keep in mind though that
it will be harder to engage with everyone if you're remote.
We'll review your spec and get you feedback, but the purpose of the sprint
(Aug
Denis,
Now that I have better understanding of the history of the commit, I
understand that this was the best way through. The Sahara and Murano team's
effort was invaluable in getting these fixed up and in a good state. I
apologize that I have raised this as an issue. I was very concerned with
Hi, folks.
I understand it may be not a good time but I want to make a proposal
regarding this feature.
The feature may be extremely useful for plugin developers if these labels
would be serialized into astute.yaml. They may be used by plugin tasks to
do node-specific modifications. Let me
OK, get it.
-Yingxin
From: Tim Hinrichs [mailto:t...@styra.com]
Sent: Thursday, July 23, 2015 11:18 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress] Need reviews of bp rpc-for-dse
Hi Yingxin,
We definitely want details for what you
On Thu, Jul 23, 2015 at 8:40 PM, Andrew Woodward xar...@gmail.com wrote:
Denis,
Now that I have better understanding of the history of the commit, I
understand that this was the best way through. The Sahara and Murano team's
effort was invaluable in getting these fixed up and in a good
Hello Tang, Openstack slaves only have a single executor so what you are
probably seeing is due to using build slaves that have multiple executors.
There were a few bugs[1] that was fixed recently around these types of
deadlock issues. The new gearman-plugin release[2] contains fixes for
those
?Evgeny/Sam/Radware,
https://os-ci-logs.radware.com/179818_27_2015-07-18_10-08-37/lbaas_v2_tempest_tests.log
The test_members module changed names. Should be as easy as just renaming the
import. I'd also check for other module renames as well.
Thanks,
Brandon
On 7/23/2015 2:45 PM, Kevin Benton wrote:
We ran in to this long ago.
What are some other examples? We've be good about keeping the network L2
only. Segments, VLAN transparency, and other properties of the network are
all L2.
The example you gave about needing the network to see the grouping
The LDAP driver for identity shouldn't require write access to look up
groups. It'll only require write access if you want to allow Keystone to
create/delete/update new groups.
Not sure what you mean by requires an LDAP admin to set up groups
separately either. Have any more details you can share?
Julian,
You want this hybrid backend driver. Bind against LDAP for auth, store
everything else in mysql:
https://github.com/SUSE-Cloud/keystone-hybrid-backend
We maintain our own fork with has a few small differences. I do not use the
assignment portion of the driver and I'm not sure anyone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
Wow! What a great week for RST conversion patches! As I write this,
there are only a handful of outstanding sections on the Cloud Admin and
HA Guides, and well over 40 sections have now been converted on the
Install Guide, with the
Hello,
I am relatively new to Openstack and Keystone so please forgive me any
crazy misunderstandings here.
One of the problems with the existing LDAP Identity driver that I see
is that for group management it needs write access to the LDAP server,
or requires an LDAP admin to set up groups
Thanks Ed for the explanation
what is the meaning of contained support. api calls, for example
GET /v2.1/os-quota-sets/{tenant_id}} was not working.
But /v3/os-quota-sets/{tenant_id} was working fine
whether I am missing something ?
On Wed, Jul 22, 2015 at 9:48 AM, Denis Egorenko degore...@mirantis.com
wrote:
Hi Andrew!
Sahara already merged. All CI tests were succeeded, also was built custom
iso [1] and ran bvt tests [2], which also were succeeded and we got +1 from
QA team.
For Murano we will do the same: resolve all
On 07/23/2015 12:43 PM, Ryan Brown wrote:
On 07/23/2015 12:13 PM, Jay Pipes wrote:
On 07/23/2015 10:53 AM, Bunting, Niall wrote:
Hi,
Currently when a body is passed to an API operation that explicitly
does not allow bodies Glance throws a 500.
Such as in this bug report:
On 07/23/2015 11:44 PM, Asselin, Ramy wrote:
Are you running on 'master' nodes? I remember seeing an issue where with a
recent version of Jenkins or a plugin where it doesn't execute jobs on the
master node.
But when run on non-master jenkins slaves, it works fine.
I checked my
Hi
As people join mid-cycle meetup, we cancel nova API meeting this week.
Thanks
Alex
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On a general topic of wiki cleanup, what's the preferred mechanism for
documenting APIs?
Wiki page [1] largely duplicates the content of the spec in [2]
I dislike duplication of information because it's likely to get out of
sync. I'd rather use hyperlinks whenever possible. However, linking to
Is it possible to delete dead blueprints or at least change the section
at the top to just provide a URL to the blueprint that supersedes it?
Blueprint [1] links to a bunch of abandoned reviews and references its
parent Blueprint [2] which also links to abandoned work. The current
work on
We have been making some progress on improvements to the Community App
Catalog, but this last month things have slowed down some. I wanted
to send a note to the mailing list to get a conversation going about
what we need to get on the roadmap, and hopefully get some folks
committed to helping
On 07/24/2015 12:00 PM, Tang Chen wrote:
On 07/24/2015 10:08 AM, Tang Chen wrote:
On 07/23/2015 11:44 PM, Asselin, Ramy wrote:
Are you running on 'master' nodes? I remember seeing an issue where
with a recent version of Jenkins or a plugin where it doesn't
execute jobs on the master node.
Hi Chandeep, The official dates of the meet up are
When:
August 05-06 2015.
Where:
HP Building 6
Lower level (street level) Room C6/7 (6LC7/9)
3404 E Harmony Rd (Ziegler), Fort Collins, CO 80528, United States
The information is at the Etherpad. We'll probably start at around 8:30 or
9:00 AM
Hi All,
Can you please tell me whether nova supports v2.1 api calls now. If
so can you please tell me where the code is located.I can see the codes for
v2(quotas.py) and v3(plugin/v3/quots_sets.py). I was thinking that v2.1 is
equivalent to v3 calls, since the api calls are looking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/23/2015 09:16 PM, Sajeesh Cimson Sasi wrote:
Can you please tell me whether nova supports v2.1 api calls now. If
so can you please tell me where the code is located.I can see the
codes for v2(quotas.py) and v3(plugin/v3/quots_sets.py). I
On 07/24/2015 10:08 AM, Tang Chen wrote:
On 07/23/2015 11:44 PM, Asselin, Ramy wrote:
Are you running on 'master' nodes? I remember seeing an issue where
with a recent version of Jenkins or a plugin where it doesn't execute
jobs on the master node.
But when run on non-master jenkins slaves,
On Thu, Jul 23, 2015 at 8:10 PM, Stephen Wong stephen.kf.w...@gmail.com
wrote:
+1 for Monday
+1 for Monday UTC. Maybe at 14 or 15h ?
On Wed, Jul 22, 2015 at 10:29 PM, Mohammad Banikazemi m...@us.ibm.com
wrote:
Gal, This time conflicts with the Neutron ML2 weekly meeting time [1]. I
From: Antoni Segura Puimedon
toni+openstac...@midokura.commailto:toni+openstac...@midokura.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thursday, July 23, 2015 at 11:16 AM
To: Mohammad
On 24 July 2015 at 05:02, Doug Hellmann d...@doughellmann.com wrote:
Because of a faulty test, we've been merging some bad requirements
changes. Please do not approve any more changes until the fixes for the
tests have been merged:
https://review.openstack.org/#/c/204181
An example/poc that adds a basic rejection mechanism to various
executors (the process pool excecutor internals are complicated and
doesn't implement it for that).
https://review.openstack.org/205262
With that the following (or similar) could be done:
http://paste.openstack.org/show/404591/
Hi Andrian,
this is High priority blueprint [1] for 7.0 timeframe. It seems we still
didn't merge the main part [2], and need FF exception for additional stuff.
The question is about quality. If we focus on enhancements, then we don't
focus on bugs. Which whether means to deliver work with lower
Sean Dague s...@dague.net wrote on 07/23/2015 01:50:00 PM:
From: Sean Dague s...@dague.net
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 07/23/2015 01:50 PM
Subject: Re: [openstack-dev] [openstack][nova] Streamlining of config
Hello everyone,
Please be informed that we have officially entered Feature Freeze state
for Fuel 7.0 Release. This means that since now on we focus on bugfixing
and stop accepting new code except bugfix commits. If you believe that
the code for your feature still needs to be merged as an
Daneyon Hansen (danehans) daneh...@cisco.com wrote on 07/23/2015
03:40:38 PM:
From: Daneyon Hansen (danehans) daneh...@cisco.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org, Mohammad Banikazemi/Watson/
IBM@IBMUS, Steven Dake (stdake)
Have we resolved this? What is the long term strategy on this?
On Mon, Jul 20, 2015 at 10:51 PM Andrew Woodward awoodw...@mirantis.com
wrote:
I found this after noon that fuel-web CI was broken due to the recent
release of oslo.config and oslo.utils 2.0.0 [1]
I attempted to muck around with
Hi,
The patch patch for fuel-library https://review.openstack.org/#/c/196114/
that implements 'compute-vwmare' role (
https://mirantis.jira.com/browse/PROD-627) requires additional work to
do (ceilometer
support.), but as far as I can see it doesn't affect any other parts of the
product.
We
$ docker -d --kv-store=consul:localhost:8500 --
label=com.docker.network.driver.kuryr.bind_interface=eth0 --
label=com.docker.network.driver.kuryr.neutron_api=10.10.10.10
--label=com.docker.network.driver.kuryr.token=AUTH_tk713d067336d21348bcea1ab220965485
Toni, Why do you want to have
On Wed, Jul 22, 2015 at 10:06 PM, Adam Young ayo...@redhat.com wrote:
On 07/22/2015 05:39 PM, Adam Young wrote:
On 07/22/2015 03:41 PM, Morgan Fainberg wrote:
This is an indicator that the bottleneck is not the db strictly speaking,
but also related to the way we match. This means we need
Gal, I vote for Monday 1600UTC.
Thanks,
Yapeng
From: Mohammad Banikazemi [mailto:m...@us.ibm.com]
Sent: Thursday, July 23, 2015 1:30 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Eran Gampel; Irena Berezovsky; Antoni Segura Puimedon
Subject: Re: [openstack-dev]
On 7/22/2015 10:18 PM, Adam Young wrote:
On 07/15/2015 06:38 PM, melanie witt wrote:
Hi Everyone,
Recently I have started reviewing the patch series about nested quotas in nova [1] and
I'm having trouble understanding where we currently are with identity v3 support in nova.
From what I
On Wed, Jul 22, 2015 at 3:00 PM, Kevin Benton blak...@gmail.com wrote:
It seems to me that the existence of the multiprovider extension is an
important point for this discussion. Multiprovider, as I understand it,
allows describing a network composed of multiple L2 segments with implicit
I a user has an admin role anywhere, they have it everywhere. This is
bug https://bugs.launchpad.net/keystone/+bug/968696 and, in order to fix
it we are going to have to adjust our thinking on policy checks.
Here is the theory:
A user is assigned a role on a project. Policy uses the roles
Or, migration scheduling would need to respect the constraint that a
port may be confined to a set of hosts. How can be assign a port to a
different network? The VM would wake up and what? How would it know
to reconfigure its network stack?
Right, that's a big mess. Once a network is picked
Hi all,
I'm using OpenStack together with OpenDaylight to add a network awareness
feature to the scheduler.
I have 3 compute nodes (one of these is also the Openstack Controller)
connected by a openvswitch controlled by OpenDaylight.
What I would like to do is to write a filter to check if a link
On Thu, Jul 23, 2015 at 8:51 AM, Kevin Benton blak...@gmail.com wrote:
Or, migration scheduling would need to respect the constraint that a
port may be confined to a set of hosts. How can be assign a port to a
different network? The VM would wake up and what? How would it know
to reconfigure
Hi,
Am I alone in thinking it's not the best use of our development
resources to throw it away and replace it with a text file that is
edited by hand?
Nope. I'm with you :)
Many people prefer vim UX instead of wandering through the semi-graphical
interface.
Are those ppl developers or
On 07/23/2015 10:08 AM, Matt Riedemann wrote:
On 7/22/2015 10:18 PM, Adam Young wrote:
On 07/15/2015 06:38 PM, melanie witt wrote:
Hi Everyone,
Recently I have started reviewing the patch series about nested
quotas in nova [1] and I'm having trouble understanding where we
currently are
Hi,
The best option is to add new functionality to fuel2 only, but I
don't think that we can do that if there is not enough functionality
in fuel2, we should not ask user to switch between fuel and fuel2
to get some specific functionality.
Do we have some list of commands which is not covered in
Unless I am mistaken, it is possible to set most of the parameters
supported by Fuel menu as kernel boot parameters. Isn't it sufficient
replacement for fuelmenu for dev's purposes?
-Oleg
On Thu, Jul 23, 2015 at 4:05 PM, Matthew Mosesohn mmoses...@mirantis.com
wrote:
How much effort are we
Tim and Masa,
Thanks very much for your invitation. I really wish I could come, but there is
a visa problem.
I’m interested in Congress implementation and will join the sprint in remote.
Hope that my idea is helpful.
Yingxin
From: Tim Hinrichs [mailto:t...@styra.com]
Sent: Thursday, July
Hi all,
During development process in nova I faced with an issue related with config
options. Now we have lists of config options and registering options mixed
with source code in regular files.
From one side it can be convenient: to have module-encapsulated config
options. But problems appear
I'm working on a draft spec[1] for a new privilege separation mechanism
(oslo.privsep) and one of the reviewers mentioned oslo.serialization. Yay.
My question is: From a quick glance over the current objects, it looks fine
atm - but is the intention that this library remain suitable for
+1
On Thu, Jul 23, 2015 at 6:14 PM, Dmitry Pyzhov dpyz...@mirantis.com wrote:
At the moment we have several core reviewers for the fuel-main project.
Roman Vyalov is responsible for merging of infrastructure-related
variables and for the lists of packages.
I am responsible for merges in
On Thu, 2015-07-23 at 17:55 +0300, mhorban wrote:
During development process in nova I faced with an issue related with config
options. Now we have lists of config options and registering options mixed
with source code in regular files.
From one side it can be convenient: to have
Are you running on 'master' nodes? I remember seeing an issue where with a
recent version of Jenkins or a plugin where it doesn't execute jobs on the
master node.
But when run on non-master jenkins slaves, it works fine.
-Original Message-
From: Tang Chen
Hi,
Currently when a body is passed to an API operation that explicitly does not
allow bodies Glance throws a 500.
Such as in this bug report: https://bugs.launchpad.net/glance/+bug/1475647 This
is an example of a GET however this also applies to other requests.
What should Glance do rather
On Wed, Jul 22, 2015 at 3:21 PM, Kevin Benton blak...@gmail.com wrote:
The issue with the availability zone solution is that we now force
availability zones in Nova to be constrained to network configuration. In
the L3 ToR/no overlay configuration, this means every rack is its own
availability
On 23 July 2015 at 05:25, Ihar Hrachyshka ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
I've stumbled on this one. It turns out we gate neutron against
openstack installation that runs vpn-agent instead of l3-agent [1]. Is
it really what we want to do?
On Thu, Jul 23, 2015 at 4:05 PM, Matthew Mosesohn
mmoses...@mirantis.com mailto:mmoses...@mirantis.com wrote:
Here's a relic of what users used to have to configure by
hand:
Hi Yingxin,
We definitely want details for what you have in mind. In case you haven't
done this before, we write a 'spec' to explain the details. Here's some
info on how to do that.
https://wiki.openstack.org/wiki/Congress#How_To_Propose_a_New_Feature
Tim
On Thu, Jul 23, 2015 at 12:13 AM
Gal,
I’m not clear exactly what you plan to do with regards to building docker
containers for Neutron, but the Kolla project has developed both linuxbridge
and ovs agents as well as a complete running Neutron system inside container
technology. We can launch it AIO with docker-compose, or
At the moment we have several core reviewers for the fuel-main project.
Roman Vyalov is responsible for merging of infrastructure-related variables
and for the lists of packages.
I am responsible for merges in make system. And I have not so much time for
digging into makefiles.
Vladimir
Oleg, those parameters are no longer documented (because there was no
validation) and are absent from the Fuel User Guide. They are,
however, still used by fuel-qa scripts.
On Thu, Jul 23, 2015 at 5:26 PM, Oleg Gelbukh ogelb...@mirantis.com wrote:
Unless I am mistaken, it is possible to set most
+1.
On Thu, Jul 23, 2015 at 6:14 PM, Dmitry Pyzhov dpyz...@mirantis.com wrote:
At the moment we have several core reviewers for the fuel-main project.
Roman Vyalov is responsible for merging of infrastructure-related variables
and for the lists of packages.
I am responsible for merges in
Dear colleagues,
What do you think of getting rid of fuelmenu and substituting it with
thoroughly commented text file + some validation + vim? The major pro of
this is that text file is easier to extend and edit. Many people prefer vim
UX instead of wandering through the semi-graphical interface.
Hi, its a friendly reminder that if you what to discuss some topics at
Rally meetings, please add you topic to our Meeting agenda
https://wiki.openstack.org/wiki/Meetings/Rally#Agenda. Don't forget to
specify by whom led this topic. Add some information about topic(links,
etc.) Thank you for your
On 07/23/2015 10:53 AM, Bunting, Niall wrote:
Hi,
Currently when a body is passed to an API operation that explicitly
does not allow bodies Glance throws a 500.
Such as in this bug report:
https://bugs.launchpad.net/glance/+bug/1475647 This is an example of
a GET however this also applies to
Hi,
can we just add all needed functionality from old fuel client that fuel2
needs, then say that old fuel-client is deprecated now and will not support
some new features, then add new features to fuel2 only? It seems like best
way for me, cause with this approach:
1. Clients will can use only
On Tue, Jul 21, 2015 at 8:41 AM, Salvatore Orlando
salv.orla...@gmail.com wrote:
It is however important to ensure services like DHCP keep working as usual.
Treating segments as logical networks in their own right is the simples
solution to achieve this imho.
Agreed.
While the logical model
Team,
I would like to request an exception from the Feature Freeze for CLI
changes of working with custom node labels added to fuelclient (fuel2) [1].
UI and Nailgun parts of the story are already merged [2].
There CLI request is being actively reviewed, the base flow is accepted.
There are
-1 for using kernel parameters for configuring the whole master node
installation. User should be able to edit configuration and then re-deploy
the master node. I have no idea what would UX look like if we used kernel
paramenters.
Vladimir Kozhukalov
On Thu, Jul 23, 2015 at 7:49 PM, Vladimir
In fact, I did an example of what I thought it would look like already:
https://review.openstack.org/#/c/205154/
I welcome discussion on this, especially from people who couldn't make
it to the mid-cycle. Its up to y'all if you do that on this thread or
in that review.
Michael
On Thu, Jul
On Jul 23, 2015, at 7:35, Adam Young ayo...@redhat.com wrote:
What this means is the if a user is assigned admin on any project, they are
assigned admin for everything.
Fixing this is going to require a change to how we write policy.
Each policy rule needs to have two parts:
1. Match
+1 on coverage of any kind.
From a tooling perspective, are you thinking istanbul?
From an infra perspective, are you thinking a separate job, or to have it
integrated in with npm run test? FYI- istanbul wraps the unit test
invocation, e.g. 'istanbul karma start ./karma.config.js' or something
1 - 100 of 162 matches
Mail list logo
