OpenStack Mitaka Aimed at Simplifying Cloud Operations (eweek.com) 20
darthcamaro writes: The 13th release of OpenStack, codenamed Mitaka is now generally available with updates across all major projects. Among the biggest new capabilities in OpenStack Mitaka however isn't a new project or a new feature in a single existing project, but rather the official debut of the OpenStack Client, which creates for the first time a unified command line interface to control the cloud.
According to eWEEK: "The OpenStack client is a command line client that unifies access across all the main projects," Jonathan Bryce, executive director of the OpenStack Foundation, told eWEEK. So if an administrator wants to create a user, a block storage device or a virtual server, or attach to a network, all those functions are now enabled in the single tool that is the OpenStack client. The OpenStack client provides a standardized set of commands, whereas previously, each project had its own command line client, Bryce said. He added that the OpenStack client can be run locally or in the cloud, and can be configured to control multiple OpenStack clouds.
According to eWEEK: "The OpenStack client is a command line client that unifies access across all the main projects," Jonathan Bryce, executive director of the OpenStack Foundation, told eWEEK. So if an administrator wants to create a user, a block storage device or a virtual server, or attach to a network, all those functions are now enabled in the single tool that is the OpenStack client. The OpenStack client provides a standardized set of commands, whereas previously, each project had its own command line client, Bryce said. He added that the OpenStack client can be run locally or in the cloud, and can be configured to control multiple OpenStack clouds.
Security? (Score:2)
Doubtful... (Score:2)
I would expect it to be more about a single utility frontending the same apis.
My bigger concern would be whether this meaningfully simplifies things, or, as is more common, is just a prefix word making commands more verbose without much benefit.
Re: (Score:3)
That sensibility is fine I suppose, but the problem is that the project has not been so restrained when it comes to how it is evangelized.
Years ago I saw a virtualization management software team pretty much get disbanded, because some high level engineer told executives that Openstack was utterly share nothing, resilient, stable, easy to use, and equipped to do everything an enterprise virtualization user would possibly want, so developing software geared toward enterprise virtualization management was a l
Re: (Score:2)
Its okay to be angry at the sales(wo)man/pitch but you are exactly right.
Re: (Score:2)
This is of course true, but a lot of the OpenStack community were pretty content to let misrepresentation in their favor run rampant, until folks started screwing themselves by listening to the hype.
Re: (Score:2)
>I don't know how it turned out, but I also was in the early stages of a very large customer datacenter revamp. They had thousands of systems largely running vmware. Their executive said 'we will move to 100% openstack within the year'. Turned out they had made this decision based solely on write ups and never actually used the software
I am AC. I am experiencing this right now...... this doesn't change the fact that we can mostly do it, but requires a complete change from how business is used to doing
Re: (Score:2)
requires a complete change from how business is used to doing things
The question being for a lot of organizations is what the upside will *really* be. Yes, if you redo a lot of your work, many things can work in that architecture. Not all things really work that well. But at the end, how do you end up better than before? Is it faster deployment of workload, lower staff cost to service requests? Could an alternative strategy have delivered the benefit in a way more compatible with the way your business works today? Will the imagined benefit really materialize given the
Re: (Score:3)
Of course, OpenStack can't implement things which are needed by real people. Wake me up when they are able to get comparable functionality to vMotion, HA, fault tolerance, or just adding disks/RAM to an image without having to kill the VM and spin up a new one from an image.
FUD. OpenStack is not a hypervisor, it's an omnibus cloud application suite. There are at least 2 nova-compute compatible hypervisors that can "vmotion" (which is snapshotting RAM and storage to a network block device). If you can't figu
dimothy (Score:2)
If you're going to put a comma after "OpenStack" you should also put one after "Mitaka".