Currently, K5 is available only through our sales channels. For customers who want to use K5, contact our sales or inquire using the inquiry form.
It depends on the contents and size of your system. The major benefits are speedy development and enhanced productivity as well as integration with external systems and systems with high adaptability to changes.
The results vary depending on the target system, however we reduced development time to 1/3, doubled productivity, and reduced PG size to 1/6. These values are compared with the existing solutions for rebuilding of mission-critical systems as part of building an on-premises development infrastructure service of the mission-critical job, which is one of the features we provide. It is on a case by case basis, but we believe the flexibility of development and operation is significantly improved.
It is very effective when you want to globally optimize a complex set of many clouds that were introduced mainly by on-site departments, or to review service levels of performance, reliability, security, etc. or to require integration with other systems as a result of feature enhancements. Benefits of migrating to our cloud will be greater if you consider it when you integrate operation and maintenance that require more advanced SI elements, or when you integrate clouds with mission-critical systems.
With integrated managed service including host, operations can be integrated with ease compared with developing individual systems. We plan to provide a service that enables hybrid integration between host and cloud easily, and a data store service that can support disaster recovery.
You can use it as the migration destination for your host assets. By moving host assets to a public cloud, customers can be relieved from host update tasks, and operation and maintenance tasks including those for hardware.
"K" is the first letter of "Knowledge Integration for Big Change" and "5" represents five continents with globalization of the solution in mind.
Some of the expertise provided are: SE tasks, configuration and settings of systems in operation, industry-specific business know-how, and know-how of failure investigation, isolation, and response. They are categorized into three forms of integration pattern, service component, and platform features. They are then implemented and provided as services.
It is designed to utilize the expertise of worldwide developers to respond to speedy technological innovations, enhance flexibility of application and system operation with greater compatibility with external OpenStack-based cloud solutions, and respond to diversified needs of the customers.
You can check the confirmed billing information using the K5 Portal.
Provisional billing information for the current month can be viewed in the IaaS Portal or the PaaS Portal.
DR in some regions will be considered in future versions.
It will be rolled out progressively from 2016.
It is a service available for customers to deploy and use virtual resources using the Service Portal/APIs. With this service, virtual systems can be built in a short period of time.
"Pay-per-use" service billed according to usage time/volume. There are no initial costs or minimum usage fee. Refer to the price list for details.
You can check your usage details in the Service Portal.
The user name and password at the time when they were issued are related to the service infrastructure, and are not published. Therefore, you need to set and deploy your password in API at the moment.
As you are aware, any communication responses allowed by Ingress rules can be communicated for firewall/security groups. The opposite is also true.
FQDN is used so that API operations by users and administrators, and increase, decrease or changes of external IP using autoscaling that will be implemented are transparent. Therefore, external IP address of the router, and external IP address after NAT conversion are not published.
Connection tracking feature is not provided for individual application that uses different TCP/UDP port from that of the initial connection.
NAT IP conversion process is performed first, and then firewall filtering is performed using the generated IP.
Global IP addresses can be used for communication between projects.
By definition, it is specified that one virtual network corresponds to one subnet, so the same number of virtual networks as that of subnets need to be created if multiple subnets are required.
The IP address for the load balancer is used as the source IP address when communicating with the distribution destinations whether SSL-TCP or TCP-TCP is used.
You can specify only one protocol and one port to be used for transfer to a virtual server. Therefore, any communication that configures multiple ports is not supported.
No NTP servers are currently available. We are considering whether to offer this feature in future versions.
It is PaaS based on the open source standard Cloud Foundry. As an application execution environment is provided, customer applications can be quickly built. The service integration feature can be used to provision services provided by the cloud native infrastructure service, FUJITSU Cloud Service K5 CF (to be provided starting with the "logging and monitoring relational database" feature), and call them from an application.
Note: Available as a trial service until April 2016.
It is the name of a standard open source Platform as a Service (PaaS) software.
Currently, only "relational database" service is available. More services will be added later.
This cannot be done. Add to or delete from cf CLI as required.
Java, Node.js, Go, Python, and PHP.
There is no plan to add libraries to buildpacks based on user specific considerations. You need to deploy necessary libraries for your applications.
Use the ’cf push’ command to deploy the developed application to FUJITSU Cloud Service K5 CF.
It is PaaS that supports agile development of highly maintainable applications and that provides an application execution environment.
It can modernize obsolete assets and deliver a robust system that can respond to changes in business.
Using its development tools, you can significantly reduce development time, improve maintainability and operability, and reduce development time.
A system can be built by simply selecting an execution environment definition (system configuration package) and deploying developed assets.
It is a comprehensive package for building an application execution infrastructure that includes Web/AP/DB, and load balancer environment definitions. It is a package verified in terms of robustness and operability, so you do not need to design your environment yourself.
Currently, we only offer two kinds of small system configuration packages, but more packages will be added in the future.
Currently, Web/AP instances cannot be automatically increased or decreased (auto-scaled), but the auto-scaling feature will be provided in the future.
The tools include Eclipse plug-ins and frameworks that deliver highly maintainable and operational application development. Customers using PF can download the development tools for application development. Refer to the following for details on the development tools.
The environment will be deployed in about two business days from the time an application is received from the Service Request Form window of the PaaS Portal.
It supports the Java language.
It is a gateway service that is provided as one of the PaaS of FUJITSU Cloud Service K5.
It delivers benefits to the providers of Web API services and customers who plan to develop Web API interfaces.
It functions as a gateway between the service that provides the API and the client application that uses it.
It has various features such as traffic control, authentication, security, and payload processing.
API Management allows these features to be deployed to an API. It also allows the development of APIs.
Some of the benefits are as follows:
API development cost reduction, because features can be added without coding.
Development efficiency, thanks to features such as debug, deploy, and development environments.
Detailed API statistics information is provided graphically, which helps improve performance, detect errors, and check usage.
API products can be provided with flexibility according to any business plan using the API' s packaging feature.
Any HTTP-based service can be specified as long as they can be accessed using the Internet.
The four major categories of features shown below can be added to an API:
Number of requests issued per unit time
Number of simultaneous connections to a back-end service
Data format conversion
Request/response data editing
API key authentication
Mashup of response data received from multiple back-end services
You can check the following using the Analytics feature:
Number of responses
Cache hit rate
Statistics for each app that executed requests
With view per API Proxy or per app, and filtering and drill-down features, you can check detailed statistics.
The environment will be deployed in about three business days from the time an application is received from the Service Request Form window of the PaaS Portal.
Diese Seite teilen