Skip to content
This repository has been archived by the owner on Nov 25, 2020. It is now read-only.

Install and run Xapi #51

Merged
merged 1 commit into from
Feb 12, 2015
Merged

Install and run Xapi #51

merged 1 commit into from
Feb 12, 2015

Conversation

djs55
Copy link
Member

@djs55 djs55 commented Feb 10, 2015

  • VMs can be uploaded and run via the XenAPI and xe
    • The mirage-generated .xe file works
  • The host can be managed via XenCenter (and presumably XenOrchestra)
  • Historical performance metrics are gathered by xcp-rrdd
  • VM disks are stored as thinly-provisioned LVM volumes, via ezlvm
  • The host physical networks are managed by xcp-networkd
    • Note the default bridge name is now xenbr0 rather than br0

Note that Xapi runs in parallel with other 'toolstacks' so it is still
possible to use xl or libvirt.

Signed-off-by: David Scott dave.scott@citrix.com

- VMs can be uploaded and run via the XenAPI and `xe`
  - The `mirage`-generated .xe file works
- The host can be managed via XenCenter (and presumably XenOrchestra)
- Historical performance metrics are gathered by `xcp-rrdd`
- VM disks are stored as thinly-provisioned LVM volumes, via `ezlvm`
- The host physical networks are managed by `xcp-networkd`
  - Note the default bridge name is now `xenbr0` rather than `br0`

Note that Xapi runs in parallel with other 'toolstacks' so it is still
possible to use `xl` or `libvirt`.

Signed-off-by: David Scott <dave.scott@citrix.com>
@djs55
Copy link
Member Author

djs55 commented Feb 11, 2015

Not entirely perfect yet, but it is now running mirage-www on my cubie@home. The future is here!

@avsm
Copy link
Member

avsm commented Feb 11, 2015

This is really wonderful, thank you!

@avsm
Copy link
Member

avsm commented Feb 11, 2015

I'm wondering what the best way to merge this is. Should be have an alternate build with XenServer, or just bite the bullet and not support a non-XS image on ARM? There's a lot of benefit in just having the nice storage and XML-RPC APIs, particularly with a view to monitoring and building a distributed ARM cloud in the future.

@djs55
Copy link
Member Author

djs55 commented Feb 11, 2015

On 11 Feb 2015 11:02, "Anil Madhavapeddy" notifications@github.com wrote:

I'm wondering what the best way to merge this is. Should be have an
alternate build with XenServer, or just bite the bullet and not support a
non-XS image on ARM? There's a lot of benefit in just having the nice
storage and XML-RPC APIs, particularly with a view to monitoring and
building a distributed ARM cloud in the future.

I believe that it's still possible to manage your VMs manually with
xl/libxl or with libvirt -- this change gives you an extra option. Xapi
will manage its VMs only; libvirt will manage its VMs only; and, well
xl/libxl just shows you everything (expert user mode?)

The only downside that I can think of is that the image is slightly bigger.

As a separate issue there are probably still some silly bugs in the .debs
I've built. Now that I'm routinely using this I should be able to squash
those and update my binary repo.

Cheers,
Dave


Reply to this email directly or view it on GitHub
#51 (comment).

@avsm
Copy link
Member

avsm commented Feb 11, 2015

Thanks, I'll merge this in after I try it on my cubie at home!

avsm added a commit that referenced this pull request Feb 12, 2015
@avsm avsm merged commit 9b2d46c into mirage:master Feb 12, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants