Well, nobody asked them to support Cloudstack earlier ...
BTW we found the Admin password thingy does not work properly, so that is being
fixed (already done in github I think).
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "ilya mu
Hi all,
I'm trying to boot instances via pxe. During my experiments that worked
a few times, but I've tried a lot and didn't document my single steps as
needed :/ Never got to a "stable" point.
By now, I'm quite unsure if a particular vm tries to boot pxe with the
default boot-order (HVM d,c)
Fo
Hi,
I am not using PXE, but can confirm that at least on KVM PXE is first method
tried - very handy.
Not sure how it is in XenServer, but I would imagine it's the same, for
consistency's sake.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Messag
I've used the iPXE iso to boot successfully multiple times. Requires
nothing on the hypervisor as far as I know, but I don't know how it works
after you have an OS installed (I'm using it to bootstrap machines).
--
Erik
On Mon, Jan 26, 2015 at 12:52 PM, Stephan Seitz <
s.se...@secretresearchfaci
Hi all,
Any news on progress with the docker container support for ACS? I've seen
a few articles on how to install CoreOS on ACS and thence docker as well as
the wish list for docker containers to be supported in ACS like LXC but I
was wondering when this'll become a reality. Also seen mentioned
I've just stumbled upon this recently
https://github.com/docker/machine/pull/129
HTH
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Osay Osman Yuuni"
> To: [email protected]
> Sent: Monday, 26 January, 2015 12:51:37
On Jan 26, 2015, at 7:51 AM, Osay Osman Yuuni wrote:
> Hi all,
>
> Any news on progress with the docker container support for ACS? I've seen
> a few articles on how to install CoreOS on ACS and thence docker as well as
> the wish list for docker containers to be supported in ACS like LXC but I
Hi Lucian,
Thanks for the pointer. I seem to be blind to the updated README referred
to in the pull request. I don't see any entry for cloudstack. Still
searching. Also I just found that there is an image for cloudstact at
CoreOS (
http://stable.release.core-os.net/amd64-usr/current/coreos_pro
What I would like to see from CloudStack + CoreOS is an integrated automatic
authentication, which would take the end user ssh keys from acs or
automatically sets a password upon creation of CoreOS instance. As far as I
recall, when I was testing CoreOS about 6 months ago, this was missing and i
I've tried following the instructions for the 4.2.x version and it is partially
working. Upon the first boot after vm instance is created from the template,
the hostname is visible at the login prompt as well as by running the hostname
command. However, after rebooting the instance, the hostname
Hi all,
we have installed a cloudstack 4.3.0 in advanced network mode on ubuntu
systems with only kvm hypervisor.
Today we received these series of notification (email):
1) Host disconnected, name: agent_name (id:7), availability zone:
zone_name, pod: pod_name
2) Host is down, name: agent_na
Andrei,
I also tried and successfully created a CoreOs template on ACS but had a
hard time authenticating. I agree that automatich authentication will be a
big boost as creating CoreOS templates for ACS have pretty much been
mastered.
Osay
On 26 January 2015 at 16:54, Andrei Mikhailovsky wrote:
Seb,
When you say "can install on their cloudstack setup" what do you exactly
mean? I have downloaded the "template" which is in a .bin format. Do I
have to run this on a VM as you suggest or how do I for example get it in a
.vhd format for a Xenserver hypervisor in ACS?
Osay
On 26 January 201
Hi,
I wonder if somebody experienced a similar issue. We have a very busy dev
cloudstack installation with 10 hosts, 3 clusters and more than 300 user VM's
running across the clusters. The cpu over-provisioning is set to 3. From time
to time we are getting the following an error when starting
From the logs it appears that agent got connected but can't say what happened
next. Need further logs.
There are quite a few things that you could verify/check, like,
1. netstat shows a connection between mgmt. server (on port 8250) and systemvm.
2. the disk on the systemvm hasn't run out of spa
Osay,
You might want to get in touch with its creator, I do not know any details.
https://github.com/svanharmelen
HTH
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Osay Osman Yuuni"
> To: [email protected]
> Sent: Monday
Yes, seen this quite a few times. I believe you already found CLOUDSTACK-2344.
Basically, the issue happens when cloudstack's view of available memory is out
of sync (more) than that of XS. This could happen due to incorrect calculation
of memory overhead and Dom0 memory. It is also possible tha
Hi Somesh,
Thank you for the reply, yes I found the issue in the Jira.
The affected host was running about 31 VM's and we don't use memory over
provisioning at all. Unfortunately cloudstack fails to restart he VM and it is
a big issue for us as the restart is a part of a nightly job and we p
Dockers networking model is rather complex (to say the least).
LXC would be the way to go, though it does not have as much marketing as
docker does.
Regards
ilya
On 1/26/15 4:51 AM, Osay Osman Yuuni wrote:
Hi all,
Any news on progress with the docker container support for ACS? I've seen
a f
Yes, XS will have the correct view since it is the one that's managing the
memory. The problem is the way CS calculates the memory overhead. I don't think
there is much we can do in terms of configuration.
This is how CS arrives at total ram:
ram = (long)((ram - dom0Ram - _xsMemoryUsed) * _xsV
Hi All,
I got some issue creating valume snapshot. Cloudstack is reporting that
quota is exceeded. But that particular account that im trying to create
snapshot for doesn't has any snapshots. Secondary storage utilization shows
200G out of 2Tb. Limit for account is 1Tb, dabase shows that account h
Going LXC might be missing the point. I don't think people go Docker because
they want containers foremost;
they do because hey want an easy way to ship applications and configurations.
Going LXC will do nothing for these people.
/imho
Lucian
--
Sent from the Delta quadrant using Borg technolog
I'm setting up a test zone for a multi-site deployment, and I've thus
far been unable to deploy a VM from our existing templates.
We're using S3 for secondary storage, and we have set up an NFS
staging server in the remote zone. The management server is able to
mount the NFS store over the site-t
Nope, i'm not missing the point, just speaking to folks who run large
docker implementations for quite sometime and moving away from it into
LXC world.
Btw, shipping container - implies shipping a tar file with metadata.
On 1/26/15 11:44 AM, Nux! wrote:
Going LXC might be missing the point. I
So it looks like the templates are searched for in
"template_zone_ref," and if they aren't found there it throws the "not
available" error.
The problem is that there is not currently a way to update the
"cross_zone" variable for existing templates.
I would think running "Copy Template" would work
Hi Nux!,
I got it at last.
Thx.
On 26 January 2015 at 17:46, Nux! wrote:
> Osay,
>
> You might want to get in touch with its creator, I do not know any details.
> https://github.com/svanharmelen
>
> HTH
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>
>
26 matches
Mail list logo
