Background: Magnum ( an Openstack Component ) was registered by Adrian Otto in 2014 as Containers as a Service. After that it got lot of popularity in the Community as containers in itself is a huge domain ( it's own user base ) and providing it as a service in Openstack attracted most users.
Then many features included, proposed by community members and it's domain kept on diverging as as containers domain in itself is too vast. Then finally in Newton Design summit community members and Openstack Technical committee (TC) collectively decided to narrow down the scope of Magnum and this lead to Magnum as Container Infrastructure Management service.
The narrow scope resulted in a new component: Zun ( formerly Higgins ). So, here is Magnum's new mission statement:-
"To provide a set of services for provisioning, scaling, and managing container orchestration engines(COEs)."
So, in this blog i will focus in Magnum Architecture (it's different components), it's Source Code, How to Contribute to Magnum, Features currently available and upcoming features.
Then many features included, proposed by community members and it's domain kept on diverging as as containers domain in itself is too vast. Then finally in Newton Design summit community members and Openstack Technical committee (TC) collectively decided to narrow down the scope of Magnum and this lead to Magnum as Container Infrastructure Management service.
The narrow scope resulted in a new component: Zun ( formerly Higgins ). So, here is Magnum's new mission statement:-
"To provide a set of services for provisioning, scaling, and managing container orchestration engines(COEs)."
So, in this blog i will focus in Magnum Architecture (it's different components), it's Source Code, How to Contribute to Magnum, Features currently available and upcoming features.
No comments:
Post a Comment