2
This charm installs the base xCAT application on either amd64 or Power architectures. The installation steps follow
3
the instructions given in the Sourceforget.net documentation:
2
This charm installs the a basic xCAT application on either amd64 or Power architectures.
3
The partially installation steps follow the instructions given in the Sourceforget.net documentation:
5
5
http://sourceforge.net/p/xcat/wiki/Ubuntu_Quick_Start/
7
This documentation can help users customize their system post-install.
10
Step by step instructions on using the charm:
7
There are suggested pre-installation and post-installation steps that the user should follow.
11
There are two assumptions made pre-execution of the xCAT charm:
13
a) There is a defined domain name that will propagate in the container in which xCAT will be installed.
14
If a defined domain name is not avialable at container creation time, then the xCAT installation will
17
b) The default repository for xCAT is found on sourceforge.net.
19
If the user chooses to customize the domain name or use an alternate xCAT respository, they may alter the
20
installation parameters with yaml-based file re-defining two parameters (listed with their default values):
24
XCAT_REPO="sourceforge.net"
26
If XCAT_DOMAIN is not altered by the user, the charm will create a container based on the default domain name of
27
the system, even if one does not exist.
31
If the user chooses to customize the either of the two variables with a custom yaml file, then the xCAT deployment
34
juju deploy --config override.yaml xcat
36
If the user chooses to go with the default values then:
39
After the deployment, the user should expose the xCAT chamr via:
43
# Post-installation configuration
45
Due to the specific nature and use of xCAT, users will want to customize networks, images, and clients
46
serviced by xCAT. Thus, only part of the Quick Start installation instructions were implemented by
47
the charm. The user should browse the Quick Start guide for customization steps:
49
http://sourceforge.net/p/xcat/wiki/Ubuntu_Quick_Start/#configure-xcat
51
Access to the container is achieved through:
16
The user can then browse to http://sourceforge.net/p/xcat/wiki/Ubuntu_Quick_Start/
17
in order to further customize the charm instance. Note that this charm only does
18
the bare essential installation of the charm. The user must then customize the network
19
and host images to their specific needs.
21
## Known Limitations and Issues
55
# Known Limitations and Issues
23
57
When this charm attempts to deploy, and there is no host or domain entry configure in /etc/hosts, then this charm will
24
58
halt and log this failure in the juju debug-log. An override variable for the domain is provided in the install script.
25
If the user fills in a value for OVERRIDE_DOMAIN within the install script, then if no domain name is found the user-provided
26
domain will be configured in /etc/hosts and the charm installation will go forward.
30
This charm does not provide post-installation configurtion after the base install of xCAT. Refere to the Quick Start
31
document referenced earlier for suggested post-install configuration steps.
59
The user should create a yaml file which contains override variables. Then, the charm should be deployed referencing
60
these override variables.
62
If no override domain is provided AND the provisioned container is not configured with a domain name, the charm installation
33
66
# Contact Information
71
# Online Documentation
73
http://sourceforge.net/p/xcat/wiki/Ubuntu_Quick_Start/
74
http://sourceforge.net/p/xcat/wiki/Ubuntu_Quick_Start/#configure-xcat
75
https://juju.ubuntu.com/docs/charms-config.html
78
# Sample yaml file to override variables
80
XCAT_DOMAIN: "your-domain"
81
XCAT_REPO: "alternate-xcat-repo"