OSCM 17.4

 What's new?

Event-based Provisioning with Kafka

This release provides for the integration of event-based provisioning systems with Apache Kafka.

A first pre-release of such a system based on an OSCM microservice framework can be found
here. It uses Kubernetes Helm for installing and managing containerized applications in Kubernetes.

Detailed information on how to use the new feature can be found here.

Specification of a Marketplace ID

When a marketplace is created, it is now possible to optionally specify an ID. If nothing is specified, the system still generates the ID automatically. This option is also available using the API.

 Getting OSCM 17.4

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 17.3

 Getting OSCM 17.3

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 17.2

 What's new?

Obtaining Subscription Usage Data

A platform operator can now create a report listing all currently active subscriptions of all customers, including the number of virtual machines (VMs) booked with subscriptions to IaaS services, for example, in OpenStack. The report also shows the number of users assigned to the subscriptions. This data can then be passed to suppliers so that they can charge customers for their usage of VMs.

APP Configuration in Web Interface

The APP administrator can now change some configuration settings for APP using the APP Web interface where service controllers are registered. The new settings overwrite the ones stored in the bssapp database as imported via the configsettings.properties file when APP was deployed.

Configuration of Ports for the OSCM Glassfish Domains

The glassfish.domain.WS_PORT configuration setting has been renamed to glassfish.domain.WS_PORT_SECURE. This setting defines the port used for a secure HTTP listener for Web service connections of the application server. The listener now uses SSL with the default application server certificate (s1as).

Extension of Parameter Configuration Tool Sample

The parameter configuration tool sample included in the OSCM integration package has been extended. It is now possible for customers to view the price per subscription for a parameter when subscribing to a service. The parameter tool API has also been extended by methods for retrieving information on parameter prices for a subscription and per user.

The sample UI supports for parameter prices for subscriptions. The API does not support stepped prices. In addition, currencies are not displayed/displayable.

 Getting OSCM 17.2

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 17.1

 What's new?

Managing HEAT templates

The OpenStack service controller now supports for managing HEAT templates allowing to deploy multiple VMs. The technology manager now has the option to import templates that can be referenced in a technical service definition into the APP database. The graphical user interface for configuring the OpenStack service controller has been extended so that templates can be imported, exported, and removed in the APP database. If a template with the same name is imported twice, the original (first) one is replaced by the second one.

APP Configuration in Web Interface

The APP administrator can now change some configuration settings for APP using the APP Web interface where service controllers are registered. The new settings overwrite the ones stored in the bssapp database as imported via the configsettings.properties file when APP was deployed. The following settings can be edited:

• APP_BASE_URL
• APP_ADMIN_MAIL_ADDRESS
• BSS_USER_KEY
• BSS_USER_ID
• BSS_USER_PWD

 Getting OSCM 17.1

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 17.0

GlassFish Application Server V4.1.2

OSCM has been ported to Java EE 7. GlassFish Server 4.1 and a Java Development Kit (JDK), version 8, 64 bit are required now. Deployment with Oracle GlassFish Server, version 4.1.2 and JDK 8, Update 121 has been tested and is recommended. The installation scripts have been adapted accordingly. SHA256 hashing is now supported.

The OSCM Installation Guide provides detailed instruction for upgrading from previous releases.

 Getting OSCM 17.0

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.1.7

 Getting OSCM 16.1.7

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.1.6

 What's new?

AWS Integration

In the AWS integration software, the following optional parameters have been renamed in the technical service definitions: - DISK_SIZE: specifies the maximum disk size of the virtual server to be instantiated. - PUBLIC_IP: specifies whether the virtual server to be instantiated is to be assigned a public IP address. - SUBNET: specifies the subnet to which the virtual server is to be assigned.

Prior to OSCM 16.1.6, the parameters were named "diskSize", "publicIP", and "subnet". If you already created services with these names, you need to change them before importing.

Extension Interface

For secure communication, the requests sent to the Web page or Web application from a custom tab are signed by CT-MG. For this to be possible, the following configuration settings in CT-MG are required: - SSO_SIGNING_KEY_ALIAS: Alias of the private key of CT-MG to be used for signing requests - SSO_SIGNING_KEYSTORE: Keystore where the private key is stored - SSO_SIGNING_KEYSTORE_PASS: Password of the keystore

The application server used for the Web page or Web application needs the corresponding certificate of CT-MG in its truststore for verifying the signature. For the predefined custom tab for IaaS service controllers, the certificate of CT-MG needs to be available in the truststore of the application server domain used for APP. The following mandatory configuration settings for APP have been introduced in this context: - APP_TRUSTSTORE: Truststore where the certificate of CT-MG is stored - APP_TRUSTSTORE_BSS_ALIAS: Alias of the certificate of CT-MG in the truststore

The existing setting, APP_TRUSTSTORE_PASSWORD, is now mandatory.

 Getting OSCM 16.1.6

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.1.5

 What's new?

Update Search Index

A new menu option is available from the Operation menu in the administration portal: Update search index. This option has been introduced to allow the operator to explicitly re-create the search index at any time. This may be required, for example, to ensure the consistency of the search index after a database recovery. The operator can still manually delete the index files and restart the respective application server domain. By using the Update search index menu option, the operator can start the re-building of the search index based on the current data in the database. The existing index structure is overwritten. The search index is re-created online, and the operator does not need to restart any application server domain.

Improved Searching

OSCM now supports searching marketable services and subscription with partial search terms.

 Getting OSCM 16.1.5

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.1.4

 What's new?

AWS Integration

In the AWS integration software, the following optional parameters have been added to the technical service definitions:

• diskSize: specifies the maximum disk size of the virtual server to be instantiated.
• publicIp: specifies whether the virtual server to be instantiated is to be assigned a public IP
  address.
• subnet: specifies the subnet to which the virtual server is to be assigned.

Extension Interface

When creating a marketable service, a supplier can now specify that a tab is added to the Details view for subscriptions on a marketplace. In this way, a Web page or Web application can be integrated for providing detailed information on a service and its operation to customers.
Customers may open the custom tab when they display details on a subscription on a
marketplace.
To link the Web page or Web application with OSCM, the supplier defines the URL pointing to
the Web page or Web application in the service definition. The content of the Web page or Web
application is retrieved and shown on the custom tab.

IaaS Service Controller Configuration Settings

Controller configuration settings such as DOMAIN_NAME, KEYSTONE_API_URL or TEMPLATE_BASE_URL can now also be provided as service parameters. This is useful for information that may be required depending on single services. Service parameters are passed to the respective provisioning service when they are set or updated by a customer.

APP API

The version of the APPlatformController and APPlatformService interfaces has been increased. The current version delivered with this release is v2_0. Existing implementations of service controllers do not need to be changed.

Custom Tab for IaaS Service Controllers

OSCM now provides a predefined custom tab for the MySubscriptions page when users are viewing their subscriptions to an IaaS service such as OpenStack or Amazon Web Services (AWS). On the custom tab, the booked Virtual Machines (VMs) are listed with detailed Information.
Suppliers can set the tab name and the URL for accessing the custom tab when creating or updating a corresponding service. The URL is in the following format:

http://<app-host-name>:<app-port>/<service controller name>/serverInformation.jsf

or, depending on the protocol used,

https://<app-host-name>:<app-port>/<service controller name>/serverInformation.jsf

For example:

https://MyAPPHost:8881/oscm-app-openstack/serverInformation.jsf

Custom Attributes for Customers

The administrator of a customer organization can now centrally set the value for a custom attribute, for example, user credentials for accessing an IaaS account such as OpenStack or Amazon Web Services (AWS). The credentials are then used for all subscriptions of the customers of a specific supplier. In case, the password needs to be changed in OpenStack or AWS, the customer administrator needs to change it only once instead of for all subscriptions.

Encryption for Custom Attributes

Custom attributes can also be defined for holding credentials. This allows customers, for example, to set the credentials for accessing an IaaS account only once. They are applied to all the subscriptions of the customer. In case the credentials have to be changed for the customer's IaaS account, the customer administrator needs to change them only once in OSCM.

 Getting OSCM 16.1.4

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.

OSCM 16.1.2

 What's new?

OpenStack Integration

The OpenStack integration software has been adapted and extended so that it can be used with
FUJITSU Cloud Service K5, a cloud platform based on OpenStack. A sample technical service
and a corresponding orchestration template are included in the OpenStack integration package.

Controller Configuration Settings

The following configuration settings have been changed or added for the OpenStack service
controller:
• TENANT_NAME: renamed to TENANT_ID.
• DOMAIN_NAME: new setting to specify the Keystone domain. Domains have been introduced with Keystone v3. A domain is a container for projects, users, and groups in the OpenStack environment. If not specified, the default Keystone domain is used.
• READY_TIMEOUT: new setting to specify the maximum time to wait for the completion of start
and stop service operations.
The settings are available in the configsettings_controller.properties file located in
<install_pack_dir>/databases/app_db folder of the OpenStack integration package.

Technical Service Parameters

The following parameters have been added to the technical service definitions:
• STACK_NAME_PATTERN: new optional parameter for specifying a regular expression against
which stack names are checked that are entered by users subscribing to a service.
• TEMPLATE_BASE_URL: new optional parameter for specifying the URL leading to the template
file or files to be used. If not specified, the URL is obtained from the controller configuration
settings.
• KEYSTONE_API_URL: new optional parameter for specifying the URL of the Keystone API for
authenticating the user specified to access the tenant for your organization in OpenStack. If not
specified, the URL is obtained from the controller configuration settings.
• DOMAIN_NAME: new optional parameter for specifying the Keystone domain. If not specified, the
domain is obtained from the controller configuration settings.
• TENANT_ID: new optional parameter for specifying the tenant for your organization in
OpenStack. If not specified, the tenant ID is obtained from the controller configuration settings.

Service Operations

In previous releases of the OpenStack integration, the Start (START_VIRTUAL_SYTEM) and Stop
(STOP_VIRTUAL_SYTEM) operations were used to suspend and resume an OpenStack instance
(stack). Now, these operations start or stop all the servers within an instance.
New operations, Suspend (SUSPEND_VIRTUAL_SYTEM) and Resume (RESUME_VIRTUAL_SYTEM),
are available for suspending and resuming complete stacks.

AWS Integration

In the AWS integration software, the following optional parameters have been added to the
technical service definitions:
• diskSize: specifies the maximum disk size of the virtual server to be instantiated.
• publicIp: specifies whether the virtual server to be instantiated is to be assigned a public IP
address.
• subnet: specifies the subnet to which the virtual server is to be assigned.

Multitenancy Support

Single sign-on (SSO) is supported by OSCM when the system is installed in SAML_SP mode
for user authentication. In this mode, the platform operator defines an Identity Provider (IdP)
against which all users registered on the platform are to be authenticated. This initial IdP is now
associated with a "default tenant" (OSCM).
The platform operator can now define and manage additional tenants and associate an IdP
system with them. Several tenants can be associated with one and the same IdP system. Any
marketplace can then be associated with a tenant. Users of organizations having access to this
marketplace will be authenticated against the IdP system associated with the respective tenant.
The marketplace and the corresponding administration portal are "tenant-specific".
When creating or updating an organization, the platform operator can also specify a tenant. The
emails sent to the users of such an organization now contain a URL for accessing the marketplace
or the administration portal containing the ID of the tenant.
User names must be unique within the scope of a tenant. This also applies to the default tenant,
i.e. user names must be unique on the platform.
The following configuration settings have been introduced:
• SSO_DEFAULT_TENANT_ID
• SSO_SAML_ASSERTION_ISSUER_ID
Note: With this release of OSCM, the public Web Services do not yet support multitenancy,
only the default tenant is supported. This means that only the platform operator or
technology managers authenticated by the default IdP are able to integrate services.

Extension Interface

When creating a marketable service, a supplier can now specify that a tab is added to the
Details view for subscriptions on a marketplace. In this way, a Web page or Web application
can be integrated for providing detailed information on a service and its operation to customers.
Customers may open the custom tab when they display details on a subscription on a
marketplace.

 Getting OSCM 16.1.2

You can find our deliverables below, as zip files. Apart from the binaries, the zips contain the relevant documentation.

Extensive 'how to' documentation can be found in our readme.md file as well as in our official documentation. The documentation for this release can be found here.