> + destroyNode(container.getId());
> + throw new IllegalStateException(String.format("Container %s has not
> started correctly", container.getId()));
> + }
> + return new NodeAndInitialCredentials<Container>(container,
> container.getId(),
> +
> LoginCredentials.builder().user(loginUser).password(loginUserPassword).build());
> + }
> +
> + @Override
> + public Iterable<Hardware> listHardwareProfiles() {
> + Set<Hardware> hardware = Sets.newLinkedHashSet();
> + // todo they are only placeholders at the moment
> + hardware.add(new
> HardwareBuilder().ids("micro").hypervisor("lxc").name("micro").ram(512).build());
> + hardware.add(new
> HardwareBuilder().ids("small").hypervisor("lxc").name("small").ram(1024).build());
> + hardware.add(new
> HardwareBuilder().ids("medium").hypervisor("lxc").name("medium").ram(2048).build());
> + hardware.add(new
> HardwareBuilder().ids("large").hypervisor("lxc").name("large").ram(3072).build());
> + return hardware;
at the moment you can only setup cpuShares. By default, all containers run at
the same priority and get the same proportion of CPU cycles, but you can tell
the kernel to give more shares of CPU time to one or more containers when you
start them via Docker. So it is not really an information about cpu limit, so
not sure we can use it on hardwareProfiles
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/57/files#r13494140
