> On 02 Nov 2015, at 15:23, Haïkel wrote:
>
> I'd like to propose new candidates for RPM packaging core reviewers:
> Alan Pevec
> Jakub Ruzicka
>
> Both are involved in downstream RDO project and this group creation.
> Alan is part of the stable release team and Jakub
Hi,
We have weekly Nova API meeting this week. The meeting is being held
Tuesday UTC1200.
In other timezones the meeting is at:
EST 08:00 (Tue)
Japan 21:00 (Tue)
China 20:00 (Tue)
United Kingdom 13:00 (Tue)
The proposed agenda and meeting details are here:
I'd like to propose new candidates for RPM packaging core reviewers:
Alan Pevec
Jakub Ruzicka
Both are involved in downstream RDO project and this group creation.
Alan is part of the stable release team and Jakub has been working on
our tooling since the beginning.
Having them onboard as core
Hi Pino,
Please see inline.
Cathy
From: Giuseppe (Pino) de Candia [mailto:gdecan...@midokura.com]
Sent: Monday, November 02, 2015 10:22 PM
To: Cathy Zhang
Cc: Henry Fourie; OpenStack Development Mailing List (not for usage questions);
Irena Berezovsky
Subject: Re: [openstack-dev]
On Sat, 2015-10-31 at 12:08 +0800, Gareth wrote:
> Hey guys,
>
> In this summary
> https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads, there
> is a live upgrade session. But the linked the etherpad is empty:
> https://etherpad.openstack.org/p/mitaka-crossproject-upgrades .
>
> So
+1 to Evgeniy
There should be no type of restrictions that cannot be overriden by user.
On Mon, Nov 2, 2015 at 5:37 PM, Vitaly Kramskikh
wrote:
> Hi,
>
> I think having both compatibility and incompatibility lists is a good
> idea. I think we need just to show a
On Sun, Nov 01, 2015 at 10:12:10PM EST, Davanum Srinivas wrote:
> Sean,
>
> I typically switch off screen and am able to redirect logs to a specified
> directory. Does this help?
>
> USE_SCREEN=False
> LOGDIR=/opt/stack/logs/
It's not that I want to disable screen. I want screen to run, and not
The reason we don’t rely on cloudint more then we already do (sed is run via
cloudiit) is because many modern distress like CentOS and Fedora Atomic have
many parts of the host os as read-only.
I prefer the structure as it is.
Regards
-steve
From: 王华
On 11/2/2015 8:46 AM, Matt Riedemann wrote:
On 11/1/2015 2:56 AM, chandraprakash mishra wrote:
I want to just start participation in openstack-nova from low/medium
level of bugs.
I tried to list out bugs but i am confused about target .is it all bugs
based on target (Kilo,Liberty)
or we
Sean,
ah. so the tip about LOGDIR to /dev/null may work for you
-- dims
On Mon, Nov 2, 2015 at 10:36 AM, Sean M. Collins wrote:
> On Sun, Nov 01, 2015 at 10:12:10PM EST, Davanum Srinivas wrote:
> > Sean,
> >
> > I typically switch off screen and am able to redirect logs to
On 31 October 2015 at 23:06, Armando M. wrote:
> On 30 October 2015 at 23:59, Matt Riedemann
> wrote:
>> On 10/30/2015 7:41 AM, Armando M. wrote:
>>> On 30 October 2015 at 18:41, Francesco Santoro
>>>
Hi,
I think having both compatibility and incompatibility lists is a good idea.
I think we need just to show a warning if users pick options which are not
in compatibility list and disable options which are in incompatibility
list. We also need to be able to provide a message in case of
Joe Cropper wrote:
>
>> On Nov 2, 2015, at 4:50 AM, Thierry Carrez wrote:
>>
>> Antoine CABOT wrote:
>>> We are pleased to introduce Watcher, a new project in the OpenStack
>>> ecosystem. We believe that a "resource optimization" service in an
>>> OpenStack-based cloud
On 11/1/2015 2:56 AM, chandraprakash mishra wrote:
I want to just start participation in openstack-nova from low/medium
level of bugs.
I tried to list out bugs but i am confused about target .is it all bugs
based on target (Kilo,Liberty)
or we can start random bugs from _nova list bug
> On Nov 2, 2015, at 4:50 AM, Thierry Carrez wrote:
>
> Antoine CABOT wrote:
>> We are pleased to introduce Watcher, a new project in the OpenStack
>> ecosystem. We believe that a "resource optimization" service in an
>> OpenStack-based cloud is a crucial component that
On Mon, Nov 2, 2015 at 9:56 PM, Cathy Zhang
wrote:
>
>
>
>
> *From:* Giuseppe (Pino) de Candia [mailto:gdecan...@midokura.com]
> *Sent:* Saturday, October 31, 2015 10:08 PM
> *To:* Cathy Zhang
> *Cc:* Henry Fourie; OpenStack Development Mailing List (not for usage
>
On 29 October 2015 at 12:43, Major Hayden wrote:
> On 10/29/2015 04:33 AM, McPeak, Travis wrote:
> > The only potential security drawback is that we are introducing a new
> > asset to protect. If we create the tools that enable a deployer to
> > easily create and administer a
Here is a docs update [0] for the patch [1] - which is rather a
framework - being discussed here.
Note, that the tool fuel_noop_tests.rb Dmitry Ilyin wrote became a Noop
testing framework, which is Fuel specific. But the same approach may be
used for any set of puppet modules and a composition
From: Giuseppe (Pino) de Candia [mailto:gdecan...@midokura.com]
Sent: Saturday, October 31, 2015 10:08 PM
To: Cathy Zhang
Cc: Henry Fourie; OpenStack Development Mailing List (not for usage questions);
Irena Berezovsky
Subject: RE: [openstack-dev] [neutron][networking-sfc] API clarification
Hello!
Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC
in #openstack-meeting-4:
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151103
Feel free to add any items you'd like to discuss.
If our schedule allows it, we'll make bug triage during the meeting.
Hello,
The libraries from the Oslo project are used everywhere in OpenStack,
which means that a security issue in Olso code might have an impact on a
lot of other projects. This is why I am currently trying to add support
for the bandit[1] static checker in all of the Oslo libraries.
While
Cyril,
If we can add this command directly in our tox.ini and entirely avoid
having the bandit.yaml would that be even better?
-- Dims
On Mon, Nov 2, 2015 at 1:22 PM, Cyril Roelandt wrote:
> Hello,
>
> The libraries from the Oslo project are used everywhere in OpenStack,
>
Steve,actually Kub is moving to fully containerize model when you need only
kublet running at the host
(https://coreos.com/kubernetes/docs/latest/kubernetes-on-vagrant-single.html)
and all other services will come in containers (e.g. ui
http://kubernetes.io/v1.0/docs/user-guide/ui.html). So we
Ditto Ryan (regXboi) Moats
Carl Baldwin wrote on 11/02/2015 11:47:27 AM:
> From: Carl Baldwin
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 11/02/2015 11:48 AM
> Subject: Re:
On 10/29/2015 10:42 PM, Anita Kuno wrote:
> On 10/29/2015 08:27 AM, Anita Kuno wrote:
>> On 10/28/2015 12:14 AM, Matt Riedemann wrote:
>>>
>>>
>>> On 10/27/2015 4:08 AM, Anita Kuno wrote:
Learning how to debug the gate was identified as a theme at the
"Establish Key Themes for the Mitaka
Thanks, Brian. I'm planning to be there.
Carl
On Thu, Oct 29, 2015 at 10:17 PM, Brian Haley wrote:
> A few of us had a discussion this week at Summit and decided to re-start the
> weekly Neutron Distributed Virtual Router (DVR) meeting. The goal is to
> help:
>
> -
On 11/02/2015 08:11 AM, Jesse Pretorius wrote:
> On 29 October 2015 at 12:43, Major Hayden wrote:
>
>> On 10/29/2015 04:33 AM, McPeak, Travis wrote:
>>> The only potential security drawback is that we are introducing a new
>>> asset to protect. If we create the tools that enable
On Mon, Nov 2, 2015 at 12:22 PM, Cyril Roelandt wrote:
> Hello,
>
> The libraries from the Oslo project are used everywhere in OpenStack,
> which means that a security issue in Olso code might have an impact on a
> lot of other projects. This is why I am currently trying to add
On Mon, Nov 02, 2015 at 02:39:49AM EST, Oğuz Yarımtepe wrote:
> All i need is to create a firewall but instead of
> using Iptables, i want to use the hardware firewall and be able to define
> filtering rules.
In the current experimental API, Firewalls are
global in scope and cover an entire
Hi Sumit,
Can you kindly share an example yaml file for firewall. With my yaml file I
am able to create vm through heat but while creating service node it says
"Invalid file format".
Regards.
Naresh
On Mon, Nov 2, 2015 at 1:31 PM, Sumit Naiksatam
wrote:
> Hi Naresh,
Hi,
+1 to what Steven said about Kubernetes.
I'd like to add that these 3 things (pid=host, net=host, -v) are
supported by Marathon, so probably it's much less problematic for us
than Kubernetes at this moment.
Regards,
Michal
On 11/03/2015 12:18 AM, Steven Dake (stdake) wrote:
Gosh,
Hi new dev looking to contribute and am open to anything. Which projects
need resources and have some low level bugs or something similar for a
newbie to get started?
Thanks,
Lisa
__
OpenStack Development Mailing List (not
On 11/02/2015 02:06 PM, Lisa Jenkins wrote:
> Hi new dev looking to contribute and am open to anything. Which projects
> need resources and have some low level bugs or something similar for a
> newbie to get started?
>
> Thanks,
>
> Lisa
>
>
>
>
Hi Lisa,
You can start looking at bugs with the low-hanging-fruit[1] tag as they are
meant to be relatively easy bugs to help new contributors get used to the
contribution workflow for OpenStack projects.
You might also want to review the how to contribute[2] page for tips on setting
up your
On 11/02/2015 02:06 PM, Lisa Jenkins wrote:
Hi new dev looking to contribute and am open to anything. Which
projects need resources and have some low level bugs or something
similar for a newbie to get started?
Thanks,
Lisa
On 11/02/2015 02:22 PM, Sean M. Collins wrote:
On Mon, Nov 02, 2015 at 03:19:42AM EST, Daniel Mellado wrote:
Also you could set up this var
LOGDAYS=1
to limit the amount of log, althougt setting the LOGDIR to /dev/null
should work too.
That is only useful if you are doing a new run of
Matt Fischer wrote:
> I'd like to get some clarification and hopefully correction on the
> values for the two operator_roles variables. One is
> in manifests/keystone/auth.pp, and it claims "Array of strings. List of
> roles Swift considers as admin.". The other is
> in manifests/proxy/keystone.pp
Hi folks,
James Penick from Yahoo! presented a talk on Thursday about how Yahoo uses
Neutron for Ironic. I would like to follow up on one particular use case
that was discussed: Multi-IP support.
Here's our use-case for Multi-ip:
For Ironic, we want user to specify the number of IPs on boot.
On Mon, Nov 02, 2015 at 03:19:42AM EST, Daniel Mellado wrote:
> Also you could set up this var
>
> LOGDAYS=1
>
> to limit the amount of log, althougt setting the LOGDIR to /dev/null
> should work too.
That is only useful if you are doing a new run of stack.sh - it won't
handle the issue of the
On Mon, Nov 02, 2015 at 10:43:45AM EST, Davanum Srinivas wrote:
> Sean,
>
> ah. so the tip about LOGDIR to /dev/null may work for you
>
That's not going to work. LOGDIR is used in multiple mkdir calls.
--
Sean M. Collins
This has come up before.
https://blueprints.launchpad.net/neutron/+spec/dhcp-options-per-subnet
Can you file an RFE (request for enhancement) bug so we can discuss it in
the Neutron drivers meeting to see if it fits in with the plans this cycle?
On Mon, Nov 2, 2015 at 10:16 AM, Sam Betts
On 09/14/2015 02:41 PM, Monty Taylor wrote:
On 09/14/2015 04:58 PM, Brian Rosmaita wrote:
I'm not saying that there's no other way to do this -- e.g., you could do
all sorts of alternative workflows and configurations in the "regular"
upload process -- but the feedback I got can be summarized
Hi everyone,
The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday November 3rd, at 19:00 UTC in #openstack-meeting
US attendees: Remember that daylight savings time has ended :)
Meeting agenda available here:
Sofer Athlan-Guyot wrote:
> Hi,
>
> The idea would be to have some of the types defined oslo config
> http://git.openstack.org/cgit/openstack/oslo.config/tree/oslo_config/types.py
> ported to puppet type. Those that looks like good candidates are:
> - Boolean;
> - IPAddress;
> and in a lesser
On 10/24/2015 12:46 AM, Clint Byrum wrote:
Can I ask one thing though, can we use a domain name + project_name_
and not the ID?
I think we can do that. The submitted patch for the overall spec is here:
https://review.openstack.org/#/c/205629/
and the change for Keystone is here:
Hi Naresh, I believe you are hitting this bug:
https://bugs.launchpad.net/group-based-policy/+bug/1418839
Try an AWS-type template [1] and it should work. Alternatively, you
can get the HOT template to work in your local environment by applying
this small fix:
Hello Nova,
Looking at Mitaka specs, but also during the Tokyo design summit
sessions, we've seen several discussions and requests for enhancements
to the Nova SR-IOV functionality.
It has been brought up during the Summit that we may want to organize as
a subteam to track all of the efforts
Just realized that tomorrow is a non-working day in Russia due to Unity
Day.
Still will try to attend the first meeting.
Thanks,
Oleg
On Mon, Nov 2, 2015 at 9:47 PM, Ryan Moats wrote:
> Ditto Ryan (regXboi) Moats
>
> Carl Baldwin wrote on 11/02/2015
Hi Naresh, I can try and help you with this. Can you unicast the file to me?
Thanks,
~Sumit.
On Sun, Nov 1, 2015 at 10:26 PM, NareshA kumar
wrote:
> Hi,
> When I try to create a Service chain node by giving the yaml file as heat
> template it says "Invalid file
On Sat, Oct 31, 2015 at 09:11:31AM +0900, Davanum Srinivas wrote:
> Matt,
>
> 0.6.0 and 0.7.0 were released for Mitaka! not Liberty. Though yes, because
> of not having pins any library we release for Mitaka will end up being used
> with Liberty as well.
>
Hi Naresh, You should be able to use the same heat templates.
Thanks,
~Sumit.
On Fri, Oct 30, 2015 at 3:06 AM, NareshA kumar
wrote:
> Hi,
> I have tried GBP in Kilo. Now I want to try GBP+SFC integration in Kilo.
> Regarding which i have few questions,
>
> Is GBP+SFC
Hi fuelers,
Currently we are working on feature component registry [1] which should
help us to prevent not logical compositions of different components in
wizard tab during cluster(environment) creation. Now we have a mechanizm
of 'restrictions' which is not flexible for components provided by
Hi Sumit,
Thanks for your response. I am just trying to create a VM as a dumb
firewall. Attached the template file for your reference.
Regards,
Naresh
On Mon, Nov 2, 2015 at 1:34 PM, Sumit Naiksatam
wrote:
> Hi Naresh,
>
> Please send me the your template file in
Also you could set up this var
LOGDAYS=1
to limit the amount of log, althougt setting the LOGDIR to /dev/null
should work too.
Cheers
Daniel
El 02/11/15 a las 04:12, Davanum Srinivas escribió:
> Sean,
>
> I typically switch off screen and am able to redirect logs to a
> specified directory.
+1
From: Clayton O'Neill >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date: Sunday, November 1, 2015 at 5:13 PM
To: "OpenStack Development
On 10/31/2015 08:55 AM, Emilien Macchi wrote:
At the Summit we discussed about scaling-up our team.
We decided to investigate the creation of sub-groups specific to our
modules that would have +2 power.
I would like to start with puppet-keystone:
https://review.openstack.org/240666
And
Thanks for joining our team meeting today!
In case you missed it or just want to catch up with Mistral activities here’s
the meeting minutes and and full log.
Minutes:
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-11-02-16.00.html
Hey Aleksey,
I agree that we need a separate API call for VIP allocation, thought I
don't agree on some points you have proposed. See my comments below.
> use PUT to change VIPs addresses (set them manually or request
> to allocate them automatically)
PUT requests SHOULD NOT be used for VIP
Hi folks,
I'm working on the following story [1][2]:
API must allow VIP to be manually set to ANY valid IP address. If the IP on
update API is a member of any network in this environment then the address
should be put in the assignments table so that it can not be used in any
other
automatic
Auto discovery is a topic which has been discussed a few times in the past for
Ironic, and its interesting to solve because its a bit of a chicken and egg
problem. The ironic inspector allows us to inspect nodes that we don't know
the mac addresses for yet, to do this we run a global DHCP PXE
Hey folks,
We had an informal vote at the mid cycle from the core reviewers, and it was a
majority vote, so we went ahead and started the process of the introduction of
mesos orchestration into Kolla.
For background for our few core reviewers that couldn't make it and the broader
community,
For the ironic inspector to be able to inspect nodes that we don't know the
mac addresses for we have to run a DHCP rule that will respond to all mac
addresses for PXE booting the inspector ramdisk. In order to provide this
functionality right now we are running our own instance of dnsmasq,
This seems like a reasonable approach. As mentioned earlier in the thread,
our current framework allows plugins to declare which components they could
not work with, so we already have information about “incompatibility” for a
number of plugins. The issue with this approach is that, as new
On 10/26/2015 02:38 PM, Major Hayden wrote:
Hello there,
I've been researching some additional ways to secure openstack-ansible
deployments and I backed myself into a corner with secure log transport. The
rsyslog client requires a trusted CA certificate to be able to send encrypted
logs to
On Mon, Nov 2, 2015 at 12:02 PM, Steven Dake (stdake) wrote:
> Hey folks,
>
> We had an informal vote at the mid cycle from the core reviewers, and it was
> a majority vote, so we went ahead and started the process of the
> introduction of mesos orchestration into Kolla.
>
> For
Hi –
Based on this “Assuming that, it will not be routing traffic, just filtering,
and that we will be using virtual routers of Openstack”
As I understand from the email, you might be comfortable to configure the HW-FW
using the ReST API. So you can write a proxy driver and connect the HW-FW
Hi,
The main reason why I think we should get all of the three states is we
don't know exactly if those plugins (which developer didn't specify) are
compatible or not, so we should not make any assumptions and prevent
the user from enabling any plugins she/he wants. The best we can do here
is to
Hi friends,
I wrote a recap of the summit (from my perspective) that some of you may
find interesting. Feedback is very welcome. :)
http://words.jimrollenhagen.com/mitaka-summit-recap/
// jim
__
OpenStack Development
Hi,
Does anyone have any guidance for configuring magnum on OpenStack kilo? this is
outside of devstack. I thought I had it configured and when I log into horizon,
I see the magnum service is started, but when I execute cli commands such as:
magnum service-list or magnum container-list I get
Hi Steve,
Thank you for the update. This is really interesting direction for Kolla.
I agree with Jeff. It is interesting to see what other frameworks will be
used. I suspect Marathon framework is under consideration as it adds most
of the application centric functionality like HA\restarter,
I will chair the meeting. With Graham and Doug not available I
suspect it will be quick, but I want to have the meeting in case there
is followup from the summit.
Michael
On Mon, Nov 2, 2015 at 3:01 PM, Hayes, Graham wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash:
I'm trying to get DevStack to work, but am getting errors. Is this a good list
to ask questions for this? I can't seem to get answers anywhere I look. I
tried the openstack list, but it kind of moves slow.
Thanks for any help.
Regards,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I will not be able to attend the meeting tomorrow, so unless
Doug or Michael can chair, I would suggest postponing the meeting for
a week.
Thanks,
Graham
- --
*Graham Hayes
On Tue, Nov 3, 2015 at 3:04 AM Steven Dake (stdake)
wrote:
> Hey folks,
>
> We had an informal vote at the mid cycle from the core reviewers, and it
> was a majority vote, so we went ahead and started the process of the
> introduction of mesos orchestration into Kolla.
>
> For
Gosh,
Kubernetes as an underlay is an interesting idea. We tried it for the first 6
months of Kolla’s existence and it almost killed the project. Essentially
kubernetes lacks support for pid=host, net=host, and –v bind mounting. All 3
are required to deliver an operational OpenStack.
This
This is just a reminder announcement of the Community App Catalog
meeting we are planning for Thursday of this week at 17:00UTC. It
will include a recap of the App Catalog related meetings from the
Tokyo Summit, as well as other status updates.
We are also working on setting up a second meeting
On 11/02/2015 03:29 PM, Jim Rollenhagen wrote:
> Hi friends,
>
> I wrote a recap of the summit (from my perspective) that some of you may
> find interesting. Feedback is very welcome. :)
>
> http://words.jimrollenhagen.com/mitaka-summit-recap/
>
> // jim
>
>
I'm not a core dev but this is a fantastic idea which will have a huge
benefit to openstack.
Tks Geoff
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Ben Swartzlander wrote:
> After reading the wiki it sounds like we cannot simply add the core team
> as an included group. I would need to request each core team member be
> added individually. Should I make requests for the individuals? Or
> should I wait until after Tokyo when some newer better
Antoine CABOT wrote:
> We are pleased to introduce Watcher, a new project in the OpenStack
> ecosystem. We believe that a "resource optimization" service in an
> OpenStack-based cloud is a crucial component that has been missing to
> date and we have started working towards filling that gap.
>
Christopher Aedo wrote on 11/02/2015 01:04:54 AM:
> From: Christopher Aedo
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 11/02/2015 01:09 AM
> Subject: Re: [openstack-dev] How we can find list of
Hi,
On Mon, Nov 2, 2015 at 11:25 AM, Somanchi Trinath <
trinath.soman...@freescale.com> wrote:
> Hi –
>
>
>
> Based on this “Assuming that, it will not be routing traffic, just
> filtering, and that we will be using virtual routers of Openstack”
>
>
>
> As I understand from the email, you might
Anne Gentle wrote:
> I wanted to write up some of the discussion points from a cross-project
> session here at the Tokyo Summit about cross-project communications. The
> etherpad is here:
> https://etherpad.openstack.org/p/mitaka-crossproject-comms
>
> One item that came up that I wanted to
Hi,
I guest most people returned from the summit so I’d like to have a team meeting
at our usual place and time: #openstack-meeting at 16.00 UTC
Agenda:
Review action items
Current status (progress, issues, roadblocks, further plans)
Quickly highlight what we did at the summit
Discuss major
Hi-
I’m confused. Do you really have an PoC implementation of what is to be
achieved?
As I look into these type of Implementations, I would prefer to have proxy
driver/plugin to get the configuration from Openstack to external
controller/device and do the rest of the magic.
-
Trinath
From:
Bruce,
That sounds like this bug to me:
https://bugs.launchpad.net/magnum/+bug/1411333
Resolved by:
https://review.openstack.org/148059
I think you need this:
keystone service-create --name=magnum \
--type=container \
--description="magnum
Bruce,
Another suggestion for your consideration:
The region the client is using needs to match the region the endpoint is set to
use in the service catalog. Check that OS_REGION_NAME in the environment
running the client is set to ‘RegionOne’ rather than ‘regionOne’. That has
snagged others
Dear PTLs, cross-project liaisons and anyone else interested,
We'll have a cross-project meeting tomorrow at 21:00 UTC, with the
following agenda:
* Review past action items
* Team announcements (horizontal, vertical, diagonal)
* Design Summit feedback
* Proposed changes to the cross-project
Hi everyone,
Currently there are jenkins macros for Ansible role testing that cover
syntax [1] and lint [2] tests. I'd like to add a generic ansible playbook
'run' test which executes a test playbook for the role, and perhaps an
'idempotence' test which executes the test playbook twice and checks
Hi all,
We have recently meet this problem: for large scale deployment, command can
be sent concurrently, and for several times, when an instance was asked to
be delete during it is launching, we observed that the vm_state and
task_state of that instance has changed abnormally like this:
When we
Thanks robert,
I've started to tweak https://review.openstack.org/#/c/209661/ with
regard to the outcome of that (at least to cover the basics)... Should
be finished up soon (I hope).
Robert Collins wrote:
Hi, at the summit we had a big session on distributed lock managers (DLMs).
I'd just
On 11/01/2015 08:19 AM, Toshiya Shiga wrote:
Hi.
We want to implement that the project users are able to manage the users of
own's project.
We are considering some proposals for that.
which keystone project's policy is using "domain" (e.g. reseller)or is not using
"domain"?
We want a
On Mon, Nov 2, 2015 at 7:27 PM, Sean McGinnis wrote:
> Cinder Release Schedule
>
> After some discussion at the Mitaka Design Summit, the Cinder team will be
> altering our release schedule for this release to simplify deadlines and
> closer align with the established
On Mon, Nov 2, 2015 at 1:36 PM, Somanchi Trinath <
trinath.soman...@freescale.com> wrote:
> Hi-
>
>
>
Hi,
> I’m confused. Do you really have an PoC implementation of what is to be
> achieved?
>
>
No indeed. I am using iptables driver to understand the FWaaS structure and
trying to replace it
On 11/03/2015 10:51 AM, Thales wrote:
I'm trying to get DevStack to work, but am getting errors. Is this
a good list to ask questions for this? I can't seem to get answers
anywhere I look. I tried the openstack list, but it kind of moves
slow.
Best to file a bug in launchpad, and *attach
Hi, at the summit we had a big session on distributed lock managers (DLMs).
I'd just like to highlight the conclusions we came to in the session (
https://etherpad.openstack.org/p/mitaka-cross-project-dlm
)
Firstly OpenStack projects that want to use a DLM can make it a hard
dependency.
Cinder Release Schedule
After some discussion at the Mitaka Design Summit, the Cinder team will be
altering our release schedule for this release to simplify deadlines and
closer align with the established OpenStack release schedule.
Overall Deadlines for Mitaka [1]
* Mitaka-1 (Dec 1-3)
*
I want to start with a big thank you to everyone who made it to the
Community App Catalog fishbowl and working sessions last Thursday in
Tokyo. Those of us who have been working at making the App Catalog
deliver on it's potential really appreciate your attention and input -
thanks!
Though we had
On 03/11/2015 1:28 PM, "Robert Collins" wrote:
>
> Hi, at the summit we had a big session on distributed lock managers
(DLMs).
Awesome.
>
> I'd just like to highlight the conclusions we came to in the session (
>
99 matches
Mail list logo