The requirements that running a fully containerized application optimally &
effectively requires the usage of a dedicated COE tool such as Swarm,
Kubernetes or Marathon+Mesos.
OpenStack is better suited for managing the underlying infrastructure.
Mike Metral
Product Architect – Private Cloud R
On 2016-01-16 12:12:00 +0800 (+0800), Thomas Goirand wrote:
> On 01/15/2016 11:26 PM, Jeremy Stanley wrote:
> > On 2016-01-15 23:09:34 +0800 (+0800), Thomas Goirand wrote:
> >> On 01/15/2016 09:57 PM, Jeremy Stanley wrote:
> > [...]
> >>> resulting in the summary at
> >>>
On 2016-01-16 11:59:44 +0800 (+0800), Thomas Goirand wrote:
[...]
> Though we could ask copyright holders to declare giving it to the
> foundation.
[...]
Please let's move this to the legal-discuss ML. Even if I thought
copyright assignment was a good idea (which I don't), I lack
sufficient
On 2016-01-16 12:14:20 +0800 (+0800), Thomas Goirand wrote:
[...]
> I've just asked this very point with the same example to the FTP
> masters. Let's see what they say...
Please point them to the archive for this thread. Specifically it
would be helpful for them to give _you_ feedback on your
Very cool, indeed! Even myself (developer of yaql) often use yaqluator
instead of yaql CLI :)
Finally took a time to see source codes.
Few tips that you may find useful:
* The most expensive operation in yaql is YaqlFactory.create(). This
method builds a parser and it takes significant time
Ryan,
I read your response and the idea of incubators is interesting, but the
risk there is we will end up with "two core teams" with different
objectives, purpose, focus, and most importantly a lack of coordinated
efforts and thinking. I'd like to experiment with converting two of our
meetings
This seems to be a different bug than what you mentioned. When share instances
were introduced some of the keys that shares had were moved to share instances
and the database objects are created separately. POST to /shares endpoint
triggers the create API, which currently only seems to be
Hi,
I'm continuously seeing failure installing openstack with latest devstack.
It exits with the following messages:
==
ramdisk=/home/localadmin/devstack/files/images/cirros-0.3.4-x86_64-uec/cirros-0.3.4-x86_64-initrd
++ for f in '"$xdir/"*.img' '"$xdir/"ami-*/image'
++ '[' -f
Remove cloud.yaml file and try!
*os-client-config* will look for a file called *clouds.yaml*in the
following locations:
Current Directory
~/.config/openstack
/etc/openstack
Thanks
Vikram
On Jan 17, 2016 8:19 AM, "Vikram Choudhary" wrote:
> Remove cloud.yaml file try!
>
>
Remove cloud.yaml file try!
*os-client-config* will look for a file called *clouds.yaml*in the
following locations:
Current Directory~/.config/openstack/etc/openstack
Thanks
Vikram
Hi,
I'm continuously seeing failure installing openstack with latest devstack.
It exits with the following
On 01/16/2016 10:16 PM, Jeremy Stanley wrote:
> On 2016-01-16 12:14:20 +0800 (+0800), Thomas Goirand wrote:
> [...]
>> I've just asked this very point with the same example to the FTP
>> masters. Let's see what they say...
>
> Please point them to the archive for this thread. Specifically it
>
11 matches
Mail list logo