Meteos is a Machine Learning as a Service in OpenStack.
Meteos allows users to analyze huge amount of data and predict a value by
data mining and machine learning algorithms.
Meteos create a workspace of Machine Learning via sahara spark plugin and
manage some resources and jobs
On 10/17/17 12:50 AM, Michał Jastrzębski wrote:
> So my 0.02$
> Problem with handling Newton goes beyond deployment tools. Yes, it's
> popular to use, but if our dependencies (openstack services
> themselves) are unmaintained, so should we. If we say "we support
> Newton" in deployment tools,
We have two patches in Mistral that we need to back port to stable/pike.
However, they are against of stable branch management policy because they
slightly change the DB schema. The patches are the following:
Reminder that the Common Classification Framework meeting is at 14:00 UTC.
The Agenda can be found here:
Hello Masakari contributors,
I submitted a patch which fixes masakari UT codes according to oslo.context
Because oslo.context 2.19.1 adds 'project' key in context's to_dict function.
But, I realized that the latest global-requirement blocks oslo.context
So I abandoned
Emilien Macchi wrote:
> Thierry, when I read your comment on Gerrit I understand you prefer to
> amend the existing policy and just make a note for installers (which
> is I think the option #2 that I proposed). Can you please confirm
> So far I see option #1 has large consensus here,
Yes, you are right on your assumptions here. The missing feature here, is
the ability of Ironic to provide a mechanism to append standard kernel
arguments, when not netbooting. Having a way to append default parameters
to bootloader would be very useful and avoid the need of manual hacks,
at the moment the z/VM CI is posting a +1 even though the job failed. That’s
because in zuul layout.yaml the job is probably set to "voting: false.” You can
easily fix this by setting it to “true”.
For example see https://review.openstack.org/#/c/512190/
On Tue, 2017-10-17 at 10:06 +, milanisko k wrote:
> Does it mean dnsmasq was run from a stand-alone container?
Yes. There are separate containers for the ironic-inspector and
> Could you please point me (in the patch probably) to the spot where
> we configure inspector
út 17. 10. 2017 v 13:06 odesílatel Dan Prince napsal:
> On Tue, 2017-10-17 at 10:06 +, milanisko k wrote:
> > Does it mean dnsmasq was run from a stand-alone container?
> Yes. There are separate containers for the ironic-inspector and
> > Could you
thanks for the testing! I've got couple of questions...
po 16. 10. 2017 v 20:04 odesílatel Dan Prince napsal:
> On Wed, 2017-10-04 at 15:10 +0200, Dmitry Tantsur wrote:
> > (top-posting, as it is not a direct response to a specific line)
> > This is your
To be as cool as nova, we'll find nicknames until then.
We can probably start with Kevin "Destroy of Clouds" Carter.
On 17 October 2017 at 15:28, Jean-Philippe Evrard
> I'd be happy to have a room for OpenStack-Ansible.
> I'll be there, and probably
Neutron - Miguel Lavalle - mig...@mlavalle.com
On Mon, Oct 16, 2017 at 9:39 PM, Jeffrey Zhang
> I am the speaker. Michal couldn't be Sydney this summit.
> On Tue, Oct 17, 2017 at 1:05 AM, Kendall Nelson
>> Added Kolla to my
I'd be happy to have a room for OpenStack-Ansible.
I'll be there, and probably more ppl, like Kevin Carter(cloudnull) and
On 17 October 2017 at 03:39, Jeffrey Zhang wrote:
> I am the speaker. Michal couldn't be Sydney this summit.
On 17 October 2017 at 09:19, Renat Akhmerov
> We have two patches in Mistral that we need to back port to stable/pike.
> However, they are against of stable branch management policy because they
> slightly change the DB schema. The patches are the
Amrith Kumar wrote:
Thanks for sending this out. Long lines in descriptions of many events
are not being wrapped, take Rochelle's session "Refstack: OpenStack to
OPNFV, Vertical, Integrated, Interop"at 3:30pm on Wednesday.
Any chance the descriptions could be wrapped?
This is now
Can you add masakari to
https://bugs.launchpad.net/oslo.context/+bug/1721432 so we don't miss it
in the process of fixing this problem? At some point we will be
releasing a new oslo.context and we need to make sure we get all the
broken projects fixed before then.
At PTG, there were discussion around prototyping per-vendor neutron
drivers (for example ML2 drivers) within containerized neutron
Is there any design decision made? If so, please kindly share it as a
guideline for implementing vender-specific neutron drivers.Thanks a
On Tue, 2017-10-17 at 11:46 +, milanisko k wrote:
> How about the shared container? Wouldn't it be better not have to
> rely on t-h-t especially if we're "scheduling" (and probably
> configuring) the services as a single logical entity?
The containers architecture for Pike and Queens is
Thanks for your feedback, everybody. I made some more edits to the
document and tried to address the remaining comments left in the etherpad.
I think the current revision of the doc provides enough details on
the metrics and goals, so it should be ready to be added to
So, my $0.02.
A supported/recent version of a tool to install an unsupported version of a
software is not a bad thing.
OpenStack has a bad reputation (somewhat deservedly) for being hard to upgrade.
This has mostly gotten better over time but there are still a large number of
Just a heads up that the releases repo is frozen while we work through some
zuul v3 migration issues. Jobs are passing, but some of the important
post-release processing that needs to happen will require a little more
tinkering to get right.
Feel free to propose release patches, but just know
On Tue, 17 Oct 2017, at 14:15, linziw...@itri.org.tw wrote:
> and in the /%24LOG_PATH/logs/devstack-early.txt file,
> it shows
> 2017-10-17 02:49:21.324 | + lib/etcd3:install_etcd3:109: sudo cp
On Thu, 28 Sep 2017 12:51:18 -0400
Doug Hellmann wrote:
> At the Queens PTG in Denver the documentation team members present
> discussed a new retention policy for content published to
> docs.openstack.org. I have a spec up for review to document that
> policy and the
Answering to both Eric and John inline.
On 10/16/2017 07:26 PM, John Garbutt wrote:
> On 16 October 2017 at 17:55, Eric Fried > wrote:
> * Adding references to the specs: ironic side ; nova side  (which
> just merged).
I have a conflict this week with a different meeting.
I would suggest we skip this week unless there is someone who can chair
it in my absence?
Description: OpenPGP digital signature
( with clicky things: https://anticdent.org/tc-report-42.html )
we can't always hold the belief which we believe 5 years ago
After [last week's report](https://anticdent.org/tc-report-41.html) I
got into an [interesting
On 16/10/17 09:53, ChangBo Guo wrote:
The oslotest.mockpatch has been deprecated in favor of native fixtures
in  , need remove its usage in python-heatclient, python-blazarclient
, Heat/Blazar team please help review, then we'll merge 
Excerpts from Zane Bitter's message of 2017-10-16 18:10:20 -0400:
> On 14/10/17 11:47, Doug Hellmann wrote:
> > Excerpts from Zane Bitter's message of 2017-10-13 15:21:14 -0400:
> >> Replying to myself here, to avoid singling anyone in particular out. I
> >> want to rephrase the question, because
On Tue, Oct 10, 2017 at 04:34:29PM -0400, Sean Dague wrote:
> On 10/10/2017 04:22 PM, Dean Troyer wrote:
> > On Tue, Oct 10, 2017 at 1:15 PM, Andrea Frittoli
> > wrote:
> >> - we will treat +1 from infra-core members on devstack changes in the
> >> ansible bits as +2
Out-of-tree virt driver maintainers, please keep an eye on , which
will force you to update the signature of your spawn and rebuild
overrides. See the commit message for the whys and wherefores, and let
me know if you have any questions.
On 16:43 Oct 16, Mike Perez wrote:
> Hey all,
> Thanks to Jimmy McArthur for getting the schedule posted so quickly! Here's
> schedule posted on the Summit site filtering by forum related sessions:
Thanks for sharing this info, I already keep an eye on this change and
understand the reason,
so if I understand this correctly, out of tree driver only need
'allocations' to be added for spawn and rebuild function and up to the
driver to use it, correct?
Kevin (Chen) Ji 纪 晨
tldr; There's an effort to collect general documentation for new OpenStack
contributors. The content that qualifies as general so far is Git, IRC, account
setup. We are looking for help to write new content at the git repo
No that subject tag is not a
On 2017/10/18 0:05, Ben Nemec wrote:
Can you add masakari to https://bugs.launchpad.net/oslo.context/+bug/1721432 so
we don't miss it in the process of fixing this problem? At some point we will
be releasing a new oslo.context and we need to make sure we get all the broken
Thanks for the update, we can clean up this module from Oslo side.
2017-10-18 2:10 GMT+08:00 Zane Bitter :
> On 16/10/17 09:53, ChangBo Guo wrote:
>> The oslotest.mockpatch has been deprecated in favor of native fixtures in
>>  , need remove its usage in
Exactly, we found the issue yesterday and will fix it
soon, really appreciate your info and help~
Kevin (Chen) Ji 纪 晨
Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com
The OpenStack Dev Digest has been receiving great feedback from various members
of our community as being a good resource to get important summaries of threads
they might be interested in responding back to and/or being informed on.
Currently the Dev Digest gets posted by me on the
Since I'm traveling to OpenStack Day Nordic, I would have to cancel our
team meeting this week, but if you have any items to discuss plz feel free
to put them on our irc channel #openstack-cyborg
I think that we(Lance and I) from Huawei are willing to take over and
continue this feature. I hope that we can get some information and
suggestion from you. Such as: what’s the progress now? What should I do
now? IMHO, the main work now is to update and polish these two specs,
I saw your pipline.yaml and found the configurations
I think you should remove the excluded symbol because it would
filter all cpu*, disk*, memeory*, network* sources.
On Wed, Oct 18, 2017 at 11:17 AM, 李田清 wrote:
I forgot to mention that explicitly but, yes, #1 is needed only not to break
the sequence of migrations. We can manually fix the migration number in #2 just
for stable/pike but I somewhat don’t like the idea of having different
migration numbers in different branches.
It’s a good news
I am testing ceilometer workload partition. And find that if we restart
agent notification, the ceilometer-pip* queue will not have consumers any
Does anyone know this? The pipeline.yaml is here
And i also find the
I’m not too happy about the idea of creating one more subproject within
Mistral. I don’t even see now what else this new library project managed by
Mistral team will contain besides this expression utils module. I’m also not
sure about its name. We already have mistral-lib which was
Mail list logo