Knowledge Base

Topic: HmC
Transferring Files and Assets to HmC-S

Transferring Assets from HmC to HmC-S The procedure to transfer files and component software assets (such as Applications, Container Images etc.) from HmC to HmC-S is as follows: Identify the HmC Project(s) that contains assets that need to be transferred to HmC-S If you need assistance uploading files into HmC using Assets see this KB Article Tag any HmC assets that will need to be transferred to HmC as “Export” If you’re unclear how to tag an asset please consult this KB Article Submit a support ticket either via the widget on the HmC site, or by sending an email to support@cons3rt.
SMTP Relay

###HmC SMTP RELAY An HmC mail relay is only accessible from HmC systems in the Hanscom Cloud (i.e. not available from HmC systems in AWS or Azure or anywhere outside Hanscom). HmC is not planning to host an external SMTP forwarder. Please reach out to support@cons3rt.com if you have any questions about how to utilize the SMTP Relay. #####SMTP Relay Details mail.hmc.hpc.mil, port 25, no ssl, unauthenticated
Register with HmC-S (SIPR)

Registering for a HmC-S Account The process of registering for a HmC-S account is outlined below. Registration for HmC-S requires access to the SIPR/DDTE fabrics. Navigate to www.hmcs.ddte.nit-c.disa.smil.mil Hit the Register button in the upper right of the screen Fill out the form that will appear Your account has been created and needs to be approved. Within 24 hours, you will recieve an email with a notification that your account has been approved, which will provide your initial username/password for login
HmC Software Licenses

Software Licensing in HmC Licensing for systems within HmC falls into one of the 4 categories listed below: 1. Operating Systems – Covered by the cloud provider 2. DoD Wide Licenses – If there is an available DoD wide license (e.g. Tenable Nessus, Java) HmC will take care of the paperwork and request to make it available to the user community 3. Other DoD Licenses – HmC will coordinate user requirements with resources like the Mythics program office so the Government does not pay for licenses it already has
Package Repository

Overview HmC has a package repository available for Red Hat systems. HmC provided Red Hat 7 and Red Hat 6 templates are already registered with this service. Available Packages Packages are available from the following channels: rhel-6-server-rpms rhel-6-server-optional-rpms rhel-6-server-supplementary-rpms rhel-6-server-rh-common-rpms rhel-6-server-extras-rpms rhel-6-server-debug-rpms rhel-7-server-rpms rhel-7-server-optional-rpms rhel-7-server-supplementary-rpms rhel-7-server-rh-common-rpms rhel-7-server-extras-rpms rhel-7-server-debug-rpms rhel-7-server-ansible-2.6-rpms rhel-7-server-dotnet-rpms rhel-7-server-ose-3.11-rpms epel-6 epel-7 Reference The following details about the repository service are for reference: The HmC repository is located here: HmC Repo.
HmC Storage Service

HmC provides a persistent storage service as an add-on feature. Use this for: Storing persistent data Data accessibility across deployment runs Loading large files (> 3 GB) as part of asset Data backup To request the storage service for your team, please enter a support ticket. The HmC team will provide a URL and credentials to access your storage. You can connect to your HmC storage service from Linux using NFS or CIFS (with credentials), or Windows using SMB.
Logging in to HmC with a Certificate

HmC uses certificate-based authentication only. There is no username/password access to HmC. Certificate options are: DoD Common Access Card (CAC) External Certificate Authority (ECA) certificate (more info about obtaining an ECA certificate) Logging in to HmC First an foremost, ensure your certificate is loaded into your browser If using a CAC, ensure you have the proper middleware installed, and your CAC is inserted into your CAC reader If using an ECA certificate, ensure the certificate has been imported into your browser Navigate to the HmC site URL https://hmc.
Deployed System Connectivity

Outbound Connectivity Systems deployed into a cloudspace in one of the local Hanscom clouds or commercial providers (e.g. AWS GovCloud, Azure, etc.) have the ability to reach out of the enclave to the greater network to access resources. Systems deployed in other DoD cloud providers (e.g. DISA milCloud) are subject to the providers standard rules. Most ports and traffic are allowed, per the latest DoD PPS. If outbound traffic is blocked, submit a support ticket and the request will be reviewed.
vGPU Optimization

HmC has vGPU acceleration enabled across several Cloudspaces. If your Cloudspace offers vGPUs, you will see operating systems with a [GPU] suffix. We continue to improve the performance of our vGPU offering in each release, and welcome any recommendations orcomments to better support our users. Best Practices Use Chrome - Chrome offers better support for the vGPU Log in using VNC first. Configure the vGPU using the NVIDIA tools on the VM.
vGPU Capabilities

Overview HmC has implemented virtual graphics processing unit (vGPU) and graphics processing unit (GPU) capabilities to support select users that require additional resources for graphical or computational intensive applications. Capacity & Availability At this time, the vGPU resources are in a separate cloudspace. If an organization needs access, they should submit a support request. Connectivity between existing cloudspaces and the vGPU cloudspace is limited and will be opened on a case by case basis.
Source Code Accounts

HmC provides built-in integrations with SoftwareForge and DI2E for building and deploying Source Code assets that use SoftwareForge Subversion or DI2E.net Bitbucket (Stash) as a source code repository. This is done via a site specific account in SoftwareForge and DI2E and simplifies the process for managing the required credentials. To use this integration, the site account must be allowed to access your source code project. HmC and SoftwareForge Subversion Access If your subversion repository is open to the Software Forge community, no additonal steps are required If your subversion repository is private: Add the hmcbuildservice user to your Software Forge project Grant the role “Contributor” to the hmcbuildservice user.