Notes on Licensing¶

When using UForge, you have to comply with the license agreement of OSes and software which UForge handles, in particular:

• Publishing OS image of RHEL (Red Hat Enterprise Linux) subscription to public cloud

  Cloud provider has to be CCSP (Certified Cloud & Service Provider) and you must register to Red Hat Cloud Access. For more details, please confirm with cloud provider.

• Scanning server

  You have to check whether the licenses of OS and software which the source machine contains allow you to use them on the destination server which you are migrating to.

  If the source machine contains rpm packages which Red Hat provides, please ask the administrator whether UForge repository contains these packages, because UForge automatically regenerates rpm packages which the repository doesn’t contain and regenerated packages are NOT supported by Red Hat.

  On UForge Portal, you can see the list of rpm packages which the source machine contains and header In Repo tells you whether or not the package comes from the repository (Refer to Viewing a Scan). Once migration is done, you can see where the package comes from by rpm command on the destination server. If regenerated, Build Host is overwritten as uforge.

• Handling Microsoft Windows

  UForge user must acquire Windows license in order to handle Windows OSes in UForge. When publishing Windows OS image or scanning Windows server, you have to confirm usage conditions of cloud provider and virtualization software which you publish to or scan.

Creating a Linux-based Appliance¶

To create a new appliance in your private workspace:

1. Select VM Builder icon on the left.

2. On the Appliance Library page, click on create in the top right.

3. Enter the Name and Version of the appliance.

   

4. From the drop-down menus, select the operating system (distribution, release and architecture).

5. Click the create button. This creates a skeleton of an appliance template in the platform which you can now customize with operating system packages, middleware and application software.

Note

If SELinux is installed (ie the file /etc/selinux/config exists), the filesystem will be relabeled on the first boot of a UForge generated VM in order to add the SELinux context in the all system files ‘ extended attribute. At boot time, init.rc checks for the existence of /.autorelabel. If this file exists, SELinux performs a complete file system relabel (using the /sbin/fixfiles -f -F relabel command), and then deletes /.autorelabel.)

6. You should now see the appliance overview page. You can add a description to your appliance (optional) and a logo (optional). The logo format must be .jpg, .jpeg or .png.
7. An OS profile is mandatory. See Adding a New OS Profile. However, you can leave the appliance at this point and edit it later.
8. If you have made any modifications, click the checkmark to save.

Creating a Windows-based Appliance¶

To create a Windows Appliance:

1. From the VM Builder tab, select create.

2. Enter the appliance name.

3. Choose Windows from the OS Distribution drop down menu.

4. Click create.

5. From the Stack page, select the OS Profile. Each version has a Core or Full release. Click save.

   Note

   Once you have chosen the OS Profile, you cannot add any packages or run updates. The OS Profile is static. Once created, if you select OS Profile, you will only be able to view the details of the profile you selected.

6. Set the Install profile and click Save.

   Note

   Unlike Linux, the following cannot be set for Windows appliances: Keyboard, Root user, User & Groups, Kernel Parameters and Firewall.

   

7. Optionally, you can set the Activation Key as part of the Install Profile. If it is not entered in the Install Profile, the default key will be used for a 30-day trial period once the appliance is booted.

8. Optionally you can add partitions.

   1. Click on Partitioning and select Advanced Partitioning.
   2. Click on the green + sign at the top.
   3. You can modify the name and partitions type
   4. Select the filesystem to ntfs and mount point to D: (or such).
   5. Enter the size. The install disk should be 12 Gb for core versions and not less than 32Gb for the full version
   6. Check the box in the Grow column if you want the partition to be growable.
   7. Click save.

   

9. Add software bundles from the Project or MySoftware pages.

   Warning

   Software bundles included in MySoftware and Project will be put on the image disk but the UForge generation tool WILL NOT install them even if these are executable/installers files (.exe, .msi, etc.). It is up to the end user to manually complete the installation of the software bundles.

   For Windows, .exe or .msi files can be given extra parameters. The parameters depend on the .exe or .msi file, and can be used for example for silent installation, providing extra configuration values, etc.

Adding a New OS Profile¶

Every appliance must have an OS profile, which contains all the operating system packages for the appliance. UForge allows you to easily create an OS profile from a set of standard profiles. You can then add specific operating system packages.

The goal is to only include the operating system packages you require to run your application. This process is known as JeOS (Just Enough Operating System). By only using the operating system packages you need, not only do you reduce the footprint of the resulting machine image, you also make the machine image easier to maintain (as there are less updates) and (hypothetically) more secure as there will be less unwanted services started.

To add an OS profile to your appliance:

1. Double click on the appliance you want to edit.

2. Go to the Stack page.

3. Click on OS Profile in the toolbox.

4. From the drop-down menu, select the OS profile template you wish to use. The operating system packages are added automatically and your appliance revision number is increased.

   

Adding Packages to the OS Profile¶

You may want to add packages that are provided as part of the operating system distribution. To get a list of all the packages that correspond to your search criteria:

1. Select the appliance to modify and go to the Stack page.

2. Click on OS Profile in the toolbox.

3. Click on the search button in the top right hand.

4. Enter your search string. For example, add php as a search string to get a list of all the PHP packages provided by CentOS.

5. Click the search icon.

   

6. Optionally you can filter the results by selecting Show only 32-bit packages (this displays only 32bit packages available) or by entering text in the filter box.

7. Select the packages you want to add.

8. Click the save button to add the packages to the OS profile.

For more information on package updates, see Tracking OS Package Updates. If you want to make sure you always have a specific version of a package, read Making Packages “Sticky”.

Generating a Docker Image¶

To generate a machine image:

1. Go to the VM Builder tab.

2. Select the appliance from the Appliance Library.

3. Click on the generate button at the top right to display all possible image formats which can be generated.

4. Choose Container, then Docker image format.

5. You can set the disk size, then click the generate button to launch a generation in UForge for this appliance template. The following pop-up will be displayed once the generation ends on the summary view.

   

5. As indicated in the pop-up, you need to click download to download the tar.gz.
6. Run the appropriate docker import command to create the image. The appliance and docker image name will depend on the name you have given them.
7. You should now be able to see the Docker image in your library.

Modifying a Windows-based Appliance¶

For Windows-based appliances UForge will indicate the number of updates available, however you cannot use this procedure to update the packages for an existing Windows appliance.

In order to benefit from a newer version of Windows, you will have to:

1. Create or retrieve a new Golden Image. See your administrator.
2. Create a new appliance.
3. You can re-use the MySoftware components contained in the current appliance.
4. You can download from the current template the boot scripts and save them on your local hard drive. You can then upload them to the new appliance.
5. You must re-produce the configuration (Install Profile, Configuration).

Making Packages “Sticky”¶

UForge allows you to select certain packages as “sticky”. This means that during image generation, this package version is chosen regardless of the current appliance template timestamp for calculating package versions. All the package dependencies of this package are also calculated.

To make a specific package “sticky”:

1. Select the appliance you want to modify.

2. Go to the Stack page.

3. From the OS profile, click on sticky in the right hand side of the package info. The sticky button will only be visible when you scroll over this part the page. In the following image, the first package has sticky in blue because it has been applied. The second one in light blue has not yet been applied.

   

4. A pop-up window will list all of the versions of the package available, allowing you to select the version you want.

   

5. Choose the version of the package you would like, then click save.

Adding Software from the Project Catalog¶

The following describes how to add MySQL and Apache to an appliance.

1. Select the appliance to modify and go to the Stack page.

2. Click on the Projects in the toolbox. This displays the Project Catalog. The bottom table lists which projects have already been added to the appliance.

   

3. Select the projects, for example Apache and MySQL and click the down arrow button. You can scroll through the available projects or enter a search string to filter the list.

4. Click Save. These projects should now be displayed in the second table.

   

Adding Software from Your Software Library¶

You can add your own custom software either using the Software Library or by including boot scripts. My Software overlay files (for example /etc/profile.d/xxx.sh) will be run before bootscripts when the machine is booted.

The following is a list of supported file formats:

• Linux only, note by default .rpm and .deb files will be installed at generation. This can be modified when you upload the files (see procedure below):

  • .rpm (“rpm i” will be executed)
  • .deb (“dpkg -i” will be executed)

• Windows only:

  • .msi
  • .exe

• Linux and Windows compatible:

  • .tar.bz2
  • .bz2
  • .tar.gz
  • .tgz.bz2
  • .tgz
  • .gz
  • .tar
  • .zip
  • .tar.zip

To add custom software components to an appliance:

1. From the VM Builder tab, click on Software Library in the top left hand side of the UI. This opens your private Software Library.

2. Click on the add software in the top right hand side.

3. You are now prompted for the name, version and maintainer of the software component you would like to add. You can also set a tag and category. Click create to complete.

4. The software Overview page will now open. You can modify the name and version, and add a description.

5. To upload the files, go to the Files page.

   

Note

If you want to group a set of files, you can create a folder by clicking create folder. Then enter a folder name and click create folder. Now if you want to put files in this folder, click on the upload icon next to the folder name.

If you create a folder, you can then click on the pencil icon to edit the file properties. Here you can select to apply the same owner and rights to all the files added to the folder.

You can now upload the files as follows:

1. Click upload to select the files you want to add and click open.
2. Click fetch to set an archive location where the files should be retrieved. When using the fetch option you can indicate a remote URL or artifact account (for information on artifact accounts, refer to Managing Your Artifact Accounts). You can also select to have the files uploaded to the UForge by checking use cache.

6. Optionally, you can modify the default install path that will be used. If you have modified the name of your appliance, it may not be reflected in the install path.

7. By default .deb and .rpm files will be installed at generation time. Optionally you can edit the settings for those files:

   • Click on the pencil on the right hand side of your uploaded file.
   • Un-select Install this native package as part of the generation.
   • Click the check mark to save your changes.

   In this case, the .deb or .rpm archive file will be in the directory but will not be installed at generation time.

   

8. Optionally, you can select to unzip archives as part of the generation. To do so:

   • Click on the pencil on the right hand side of your uploaded file.

   • You can then edit the install path and select if it should be extracted.

   • Click the check mark to save your changes.

     

9. From the Distribution page, you can set the distributions with which your software is compatible. By default, all the distributions listed in the bottom table are compatible. If you want to remove a distribution from the list, select and click the up arrow and save.

   Note

   If you remove all the distribution compatibility, the software will not be visible for any appliances.

10. From the Repository Packages page, you can set the packages with which your software is compatible. This page will only be visible if you have selected only one distribution. You can search for packages. Select and click the down arrow to add them. Click save.

11. From the Boot Scripts page, upload any boot scripts you want to add to this software. You can either:

    • Upload an existing boot script file by using the upload icon.
    • Create a new boot script by clicking new.

    

In both cases, you must select the type. If you select first boot, then the boot script will be launched once the first time the instance is launched. If you select every boot, then the boot script will be launched every time the instance is rebooted. You must also set the boot order.

12. From the Licenses page, upload any licenses you want to add to this software. Click upload, select your license and click save.

13. Add the uploaded software component to the appliance. Click on the Appliance Library to view your Appliance Library. Double-click on the appliance template you want to add the software to.

14. Go to the Stack page and click on the My Software button in the toolbox.

    

15. Select the software components you want to add and click the down arrow button.

16. Click save to add this software component to your appliance template.

Adding Users and Groups¶

You can add operating system users and groups to the appliance Install Profile. These will be integrated to the appliance template.

To add a user to an appliance:

1. Select the appliance template you want to modify.

2. From the Stack page, click on Install Profile in the toolbox.

3. Select Users and Groups.

4. Click the plus symbol next to the Users table. The Create User page will be displayed.

   

5. Enter a user name.

6. If you want to manually enter the user ID, deselect set the user id automatically and enter the ID number.

7. If you want to manually create the primary group the user is part of, deselect automatically create primary group for user and enter the group name.

8. Click create

To add a group to an appliance install profile:

1. Select the appliance template you want to modify.

2. From the Stack page, click on Install Profile in the toolbox.

3. Select Users and Groups.

4. Click the plus symbol next to the Groups table. The Create Group page will be displayed.

   

5. Enter a group name.

6. Check if you want this group to be a system group.

7. If you want to manually enter the group ID, deselect Set the group id automatically and enter the group ID number.

8. Click create.

Advanced Partitioning for Linux¶

The following example assumes that you want to build the following partitions, with a virtual hard drive of 20 GB.:

part /boot –fstype=ext4 –size=500 –ondisk=sda
part pv.1 –grow –size=1 –ondisk=sda
volgroup ROOTVG –pesize=4096 pv.1
logvol / –fstype=ext4 –name=LogVolROOT –vgname=ROOTVG –size=3072
logvol swap –name=LogVolSWAP –vgname=ROOTVG –size=1024
logvol /usr –fstype=ext4 –name=LogVolUSR –vgname=ROOTVG –size=5120
logvol /var –fstype=ext4 –name=LogVolVAR –vgname=ROOTVG –size=1024
logvol /home –fstype=ext4 –name=LogVolHOME –vgname=ROOTVG –size=5120
logvol /tmp –fstype=ext4 –name=LogVolTMP –vgname=ROOTVG –size=1024
logvol /opt –fstype=ext4 –name=LogVolOPT –vgname=ROOTVG –size=1024

To set advanced partitioning for an appliance template:

1. Select the appliance you want to modify.

2. From the Stack page, click on Install Profile in the toolbox.

3. Select Partitioning, then Advanced Partitioning.

   Note

   In order to view the information more easily, you can click on the enlarge button in the top right. This opens a separate window where you will see all the advanced partitioning.

4. Advanced partitioning works sequentially, from top to bottom. The three sections offered by the UI, which are Disks, Logical Groups, and Logical Volumes should be filled in order, sequentially:

   • disks with partitions including the total virtual disk size required
   • logical group(s), assigning the associated physical extent (partition)
   • specify the logical volume specification for the created logical group(s)

   

5. Click on the arrow in Disks next to sda. You will see the default disks.

   

6. Delete the default linux swap partition by clicking the x at the end of the line with linux-swap. You must not set the swap size to 0.

7. Click on the size of the MSDOS partition to set it to 20000.

8. Click on the partition 1 information to modify the file system to ext4 and the mount point to /boot.

9. Click on the + sign to create a new partition with type lvm2 and size set to 18000 MB.

10. Unselect Grow and set the size of the /boot disk to 500.

11. In the Logical Groups section, click on the + sign and set the name of the logical group. For this example: ROOTVG.

    Note

    Image generation will fail when migrating if the volume group name set in the Partitioning Table is the same as the name of LVM volume group in UForge server.

12. Next to the newly created volume group, click on the + sign to create a new volume extent. A pop-up window will appear proposing a sda/2 physical extent with size automatically set to 18000 MB. Click ok.

    

13. Create the logical volumes one by one, or create them all at once and then edit the respective specifications. For each logical volume to create, click on the + sign in the Logical Volumes section. For our example, you will need seven logical volumes.

    • LogVolROOT ext4 / 3072
    • LogVolSWAP linux-swap 1024
    • LogVolUSR ext4 /usr 5120
    • LogVolVAR ext4 /var 1024
    • LogVolHOME ext4 /home 5120
    • LogVolTMP ext4 /tmp 1024
    • LogVolOPT ext4 /opt 1024

14. Click Save.

Advanced Partitioning for Windows¶

You can set an advanced partitioning table for a Windows-based appliance template. To set advanced partitioning:

1. Click on Partitioning and select Advanced Partitioning

2. Click on the green + sign at the top.

3. You can modify the name and partitions type

4. Select the filesystem to ntfs and mount point, for example: D:.

5. Enter the size. The install disk should be at least 14 Gb for core versions and 20Gb for full versions

6. Check the box in the Grow column if you want the partition to be growable.

7. Click save.

   

Adding a Boot Script¶

You can add boot scripts that will be run either the first time the appliance is booted or every time the machine or virtual machine is started. The boot scripts will be run once all the software and appliance packages are installed, prior to launching the machine. The scripts are run in numeric then alphabetical order. The boot scripts will be executed as root.

If you want to install software or packages as part of the installation, you can use My Software to upload overlay files (e.g. /etc/profile.d/xxx.sh). For more information, refer to Adding Software from Your Software Library.

To add a boot script to your appliance:

1. Select the appliance you want to modify.

2. From the Stack page, click on Configuration in the toolbox.

3. Select Boot Scripts.

4. Click on new or upload button on the right hand side.

   

If you are creating a new boot script:

1. Enter the name.

2. Select the type: If you select first boot, then the boot script will be launched once the first time the instance is launched. If you select every boot, then the boot script will be launched every time the instance is rebooted.

3. Select the boot order.

4. Enter the contents of the boot script.

5. Click save.

   

If you are uploading an existing boot script:

1. Select the type: If you select first boot, then the boot script will be launched once on the first time the instance is launched. If you select every boot, then the boot script will be launched every time the instance is rebooted.
2. Select the boot order.
3. Click choose to locate your file and click open.
4. Click save.

Exporting¶

To export an existing appliance:

1. Go to your Appliance Library
2. Click on the export icon on the right hand side of the appliance template in question to export

3. This will start the export process.

4. Once the export is complete, you will be prompted to download the archive file

The equivalent export feature is available when editing an appliance template.

Importing¶

To import an archive:

1. Go to your Appliance Library
2. Click on the import button at the top right hand side of the view

3. This opens up a file browser, choose the archive to upload
4. This will start the import process.

5. Once the import is complete, a new appliance template can be found in the Imported Appliances sub-section of your Appliance Library.

Scanning the Source Machine¶

On the scan target, the uforge-scan binary is copied and launched as root to analyze the entire system. The scan carries out the following phases:

1. uforge-scan tests the connection to UForge server with the information provided by the user in the command line.
2. uforge-scan checks the basic information of the machine (Operating System, architecture) and the installation parameters (partitioning, timezone, keyboard, etc.).
3. Analysis of the operating system native packages installed on the system. The uforge-scan binary checks which packages have been installed, the state of the files in these packages etc. The scan process registers all the metadata (rights, user and groups, checksums).
4. Analysis of the files that are not part of any operating system native packages. The uforge-scan binary registers all the metadata (rights, user and groups, checksums).

Analysis of Report¶

A report is created by the uforge-scan binary based on all the information discovered. This report is transferred via HTTPS to UForge AppCenter.

UForge AppCenter stores all the report information. This data is then processed to identify what information is missing by UForge AppCenter to rebuild the source machine. The processing includes:

• which operating system native packages UForge AppCenter does not have in its repository or in an incremental scan.
• which files from operating system native packages have been modified compared to the official native packages in the UForge AppCenter repositories.
• which files that are not part of any OS native packages and are not in any incremental scan of the same machine.

The results of this analysis are then sent via HTTPS back to the uforge-scan binary on the source machine. This is basically all the information that UForge AppCenter does not have already based on the initial report received.

Build the Overlay Archive¶

The uforge-scan binary retrieves the analysis results from UForge AppCenter. These results include a list of all the packages and files UForge requires. The uforge-scan binary builds an overlay archive of all these packages and files.

The overlay is all the things that are missing compared to a known state (a previous scan of a machine or the operating system native packages). This overlay is a standard tar archive. Once created, it is uploaded via HTTPS to the UForge AppCenter.

The overlay is not built on the scan target but it is stream uploaded (faster and does not need any space on the scan target machine).

At this stage in the process, the uforge-scan binary has finished its job and no further communication between the scanned machine and UForge AppCenter is required. For this reason, the uforge-scan binary exits.

Overlay Extraction¶

UForge AppCenter retrieves and extracts the overlay sent by the uforge-scan binary. It then recreates all the necessary OS native packages that are not present in any of the package repositories known by UForge AppCenter. The analysis and overlay processes are now finished. All the scan metadata remain in UForge AppCenter until the scan gets deleted.

You can now carry out a black box or a white box migration. For black box migration, you generate a new machine image from the scan. For white box migration, you must first import the scan as an appliance template.

Generate an Image (Black Box Migration)¶

At this stage, the scan report is used to generate a new machine image. The generation tool:

1. Returns all the packages discovered on the scan target and installs them.

2. Takes the overlay and applies it on top of the built system.

3. Tunes the machine for the target environment. This is specific to the machine image format chosen. This includes injecting extra libraries and packages required by the target environment.

4. The networking information is treated differently depending on whether the IP address of the workload being migrated is using a static IP address or DHCP.

   • Static IP Addresses: The current information detected during the scan is kept. During the generation phase, this networking information is also kept. Consequently, the new machine instance has the same static IP address set.
   • Dynamic (DHCP) IP addresses: In this case, the networking information, is reset namely the IP address information is removed during the generation process, and is setup as DHCP. When the new machine instance is provisioned, the instance sends a request to the local cloud DHCP service to get a new IP address.

In the case of a migration from a para-virtualized platform to a non para-virtualized platform, UForge AppCenter injects everything that is needed to make the machine work (the kernel and its tools). Based on the packages discovered on the scan target and on the underlying operating system, UForge AppCenter calculates the most accurate kernel version to inject for your machine.

Once the image is generated, it is possible to push it to a remote environment. The image is then ready to be launched in the new environment and the migration is finished.

Import to an Appliance Template (Whitebox Migration)¶

At this stage, the scan is used to create a new appliance template. This allows you to change and modify the contents of the machine that has been scanned.

The process of importing:

1. Creates a template.
2. Creates an OS Profile and injects all the native packages.
3. Injects the overlay as a My Software component and is added to the appliance template.
4. Sets the scanned installation configuration information in the Install Profile.

It is then completely detached from the scan and you can do exactly the same things as with any other template.

If you generate an image from this template, it will go through the same steps as a standard template generation:

1. Checks all the dependencies.
2. Installs all the packages.
3. Installs all the my software components.
4. Tunes the machine for the target environment. This is specific to the machine image format chosen. This includes injecting extra libraries and packages required by the target environment.

Once the image is generated, it is possible to push it to a remote environment. The image is then ready to be launched in the new environment and the migration is finished.

Scanning a Linux Machine¶

To carry out a scan, go to the Migration tab:

1. Click on scan in the top right.

2. Enter a name for the scan of the target system you want to migrate.

3. Select Linux from the drop-down menu.

4. If you want to exclude certain directories or files from the scan then click add and enter the directory path or full pathname of the file.

   

5. Click Next. Follow the instructions on the UForge AppCenter GUI.

6. Download binary locally by clicking Download.

7. Copy the binary on the target environment you want to migrate.

8. Open a terminal window and login to the target environment.

9. Run the scan command on the running target environment to start a deep scan of the system you want to migrate. The binary identifies the packages, files and custom files on the system.

   By default the scan data will be saved in /tmp. You can modify the directory where the data will be saved using the -t option in order to ensure that there is enough space to save the scan data.

   You can also use API keys to run the command. In this case, in the command you copied, remove the password and enter the API keys using -a option for the public key and -s option for the secret key. For example:

   ./uforge-scan.[bin/exe] -u <username> -a <public-key> -s <secret-key> -U http://ip:port/ufws -n 'Test_scan'
   

10. A report is sent to UForge AppCenter which can be used for migration. To view the progress, go back to the Migration tab and click ok.

Note

The duration of the scan depends on:

• the power of the machine in the target environment,
• the complexity of the target environment OS (number of packages installed),
• the network bandwidth between the target environment and UForge.

Scans of typical simple target environments can last about 5 to 15 minutes. In the case of larger and more complex target environments, together with poorer bandwidth, one can experience durations of up to one hour.

11. To view the details of a scan, click on the scan and refer to Viewing a Scan.

Scanning a Microsoft Windows Machine¶

To carry out a scan, go to the Migration tab:

1. Click on scan in the top right.

2. Enter a name for the scan of the target system you want to migrate.

3. Select Windows from the drop-down menu and click next.

4. Select the method you want to use: if you want to scan using an exe that will launch a graphical interface, or by downloading a zip file and launching it through command-line.

   • If you are using exe the pop up will indicate the partition being scanned and time left
   • If you choose to download the zip then you will have to launch the command as indicated.

   

5. If you want to exclude certain directories or files from the scan then click add and enter the directory path or full pathname of the file.

6. Optionally you can select Use local storage. This means that the scan will be not be done in streaming but in 2 phases. First the data will be stored on a temporary storage drive during the scan process. This temporary storage can be a local directory or a virtual space on the network. It must be at least half the size of the machine you want to scan.

   

Note

If you are using local storage you will have to launch a script at the end to upload the archive to UForge AppCenter later.

7. Optionally you can use API keys. In this case, check Use API keys authentication and enter the public and secret key information.

   

8. Click scan to launch the scan. A report is sent to UForge AppCenter which can be used for migration. To view the progress, go back to the Migration tab and click ok.

9. To view the details of a scan, click on the scan and refer to Viewing a Scan.

Inviting Members to Your Workspace¶

Once you have created a workspace, you can invite users to it. By inviting users, they will be able to view appliance templates you have added to the workspace, and depending upon their access rights share their appliance templates.

To invite users to your workspace:

1. Go to the Members page of the Collaboration tab.

2. Click on invite in the top right.

   

3. Enter the email addresses of the people you want to invite to your workspace. If the email you specify is not recognized by UForge AppCenter, you will be prompted to invite them to join the platform.

4. You can modify the invitation message. This message will be included in the email inviting members to join your workspace.

5. Click invite.

Managing Member Access Rights¶

Once a user has joined your workspace, you (or another workspace administrator) can modify their status. By default, when users accept your invitation and join your workspace they will be collaborators.

Members of a workspace are either:

• Guest. A guest can read and post to the activity stream, and import appliances into their private appliance library.
• Collaborator. The collaborator has the same basic rights as the Guest, but can also share appliances.
• Administrator. This is generally the user who has created the workspace. There must be at least one administrator in a workspace, though there can be more. The administrator can invite or delete members and is able to delete a workspace. The administrator has all the same basic rights as the collaborator.

Deleting a Member¶

If you are a workspace administrator, you can delete any member of the workspace simply by going to the Members page and clicking the small symbol to the right of the member’s name and info.