Hello
was hoping somebody might be able to help. I know it is only tech preview. but has anyone gotten docker containers to work in SuSE CLoud 6
this is my setup
I created a compute node and enabled the docker hypervisor. Then I created a separate availability zone/host aggregate with that server
I upload the docker images via docker save | glance --------------------
but when I try to boot the docker images, on the horizon, the images are running, but when I do a docker ps, I don’t see any containers running
any tips/ideas if anyone has any. Would appreciate any feedback/suggestions
I think this means that from nova perspective it seems to work fine, I would assume you don’t have error logs from nova-compute. Unfortunately, this doesn’t mean that it really works. I’ve had this with several images I tried to prepare for Openstack. After uploading and booting them, nova and horizon reported success, but actually the VM was stuck in grub menu, I could see that on xl console. So if there’s a way to get on a console or something you could maybe figure out what the problem is. I don’t have any experience with docker yet so this is all I got
Hi Bernhard, eblock
Thank you very much for your feedback. Will try to figure out what the next steps are. Have to look for some servers that can have some disks with btrfs. Currently my test environment is small and server has only 1 disk @Bernhard - will really be interested to see what SuSE is going to do moving forward e.g. OpenStack on Containers (for DB, keystone), Kubernetes, etc…
I thought the documentation already stated that btrfs is mandatory for
docker but I Would need to double check on this …[/color]
There is a note re Deploying Docker in section 10.12 of the SUSE
OpenStack Cloud 6 Deployment Guide: Deploying Nova[1] which suggests
Btrfs is recommended:
“If you assign the nova-compute-docker role to a node, it is recommended
to use Btrfs for the respective node to enhance the performance.”
@Bernhard - will really be interested to see what SuSE is going to do
moving forward e.g. OpenStack on Containers (for DB, keystone),
Kubernetes, etc…[/color]
If you are attending SUSECon 2016 you may be interested in the following
sessions:
CAS91065 - OpenStack and Magnum: Kubernetes as a Service for everyone[1]
Kubernetes is one the major orchestration solutions for Linux
containers. It makes it easy to have distributed, self-healing and
autoscaling container clusters. But operators often have a hard time
setting up a Kubernetes cluster and it can take quite a lot of effort
even for the creation of a simple cluster. Things get even more
challenging when security, flexibility and scalability have to be taken
into account. And what about making everything automated to satisfy the
requests of all the tenants? Lots of developers and operators are
running away from this complexity by using the Kubernetes offerings
inside of the public clouds. Is this the only one solution? This talk
will show how OpenStack can act as the perfect platform to run
Kuberenetes clusters by using the Magnum project. This gives you a fully
automated deployment system for cloud applications and the following
features: 1. Automatic scheduling of containers based on their resource
requirements and other constraints, while not sacrificing availability.
Mix critical and best-effort workloads in order to drive up utilization
and save even more resources. 2. Self-healing and restarting containers
that fail, replacing and rescheduling containers when a node dies,
killing containers that don´t respond to your user-defined health check
and providing containers that don´t advertise themselves to clients
until they are ready to serve. 3. Horizontal scaling up and down with a
simple command or based on CPU usage. 4. Service discovery and load
balancing. 5. Automated rollouts and rollbacks and many others. Now is
the time to give OpenStack cloud operators a self-service solution for
providing containers to their cloud users as a managed hosted service.
The OpenStack Magnum component simplifies the required integration with
Kubernetes and allows cloud users who can already launch cloud resources
such as Nova Instances, Cinder Volumes, Trove Databases, etc. to also
create application containers to run their applications.
TUT91573 - Demystifying Kubernetes: An introduction for Sysadmins & Co.[2]
As more and more users are starting to consider Docker in production
environments, people have realized that having Docker alone is not
enough. Instead, the community is gearing towards orchestration
solutions: tools, frameworks and practices that deal with how containers
are deployed on production and how administrators can monitor all this
without going crazy. Join us for this brief journey into SUSE’s
orchestration choice: Kubernetes.
