[GLASSFISH-16404] Define deployment-time service metadata for use in PaaS deployments Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: 4.0_b49

Type: New Feature Priority: Blocker
Reporter: Sivakumar Thyagarajan Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16402 Single-click application provisioning... Closed
Tags: ee7_cleanup_closed

 Description   

Service Meta-data:

  • Define a mechanism to specify deployment-time cloud meta-data (cloud.xml or any other appropriate name as we decide) that includes service definitions and service references of an application. The service reference could be a reference to an application-scoped service or global/shared service or external service
  • Optionally define glassfish-cloud.xml schema for glassfish specific defaults and extensions for cloud-metadata. This could also be used by the Orchestrator to map generic service meta-data specified in cloud.xml to a Service Template in an IMS template catalog


 Comments   
Comment by shreedhar_ganapathy [ 27/Oct/11 ]

Changed AffectsVersion to 4.0

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-16405] Automatically provision services during application deployment Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: 4.0_b61

Type: New Feature Priority: Blocker
Reporter: Sivakumar Thyagarajan Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-16423 Support the basic Paas deploy and und... Closed
depends on GLASSFISH-16424 Additional support for Paas deploy an... Closed
blocks GLASSFISH-16402 Single-click application provisioning... Closed
Tags: ee7_cleanup_closed

 Description   

Automatically provision services during application deployment:

Provision all the required dependent services during deployment of a Java EE application. The application could come up with full/partial/no cloud meta-data.

The Orchestrator would use the IaaS APIs to provision and manage the lifecycle of a Provisioned Service. The Orchestrator must be Service VM Host/Guest OS agnostic. In other words, the Orchestrator must not have any additional dependencies/restrictions on Host/Guest OS of a Service VM Image as we expect the IaaS API and implementation to handle these.

The following must be considered as part of Service Provisioning

  • Service Provider Matching (Template matching rules): Using the service meta-data bundled with or discovered from the application, the Orchestrator must match the service requirements of the application to a Service Template. This template would then be used to provision and realize the Service. These matching rules are still a work in progress. One simple rule that has been identified is: If the application requires a RDBMS service and the service definition is not specified in the cloud meta-data or the service definition does not explicit point to a particular Service Provider(say MySQL), then by default the Orchestrator will select a "default" template (e.g: Derby service template).
  • Atomic provisioning: Provisioning of the dependent services of an application must be atomic (ALL or NONE).
  • Failure handling: If a subset of dependent services cannot be provisioned, the deployment must fail and the state of the system must roll-back to the state prior to the current deployment. [Atomic deployment]
  • Ambiguity during provider matching When multiple plugins can handle particular service requirement and a particular service provider can not be matched then deployment must fail.
  • Automatically provisioning services for vanilla Java EE archives


 Comments   
Comment by Sivakumar Thyagarajan [ 21/Apr/11 ]

Updated the feature description to add additional service provisioning requirements

Comment by shreedhar_ganapathy [ 27/Oct/11 ]

Changed AffectsVersion to 4.0

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-16407] Automatic Service association for a PaaS application Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: 4.0_b55

Type: New Feature Priority: Blocker
Reporter: Sivakumar Thyagarajan Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16402 Single-click application provisioning... Closed
Tags: ee7_cleanup_closed

 Description   

Service Association/Binding

Automatically perform necessary actions(create the necessary pools/resources etc) in the application server to bind an application to the services provisioned for the application



 Comments   
Comment by shreedhar_ganapathy [ 27/Oct/11 ]

Changed AffectsVersion to 4.0

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-16403] Support External, Shared Provisioned and Application-Scoped Provisioned Services Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: New Feature Priority: Blocker
Reporter: Sivakumar Thyagarajan Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16402 Single-click application provisioning... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-17584 allow provisioning of shared services... Sub-task Closed Jagadish  
GLASSFISH-18015 Start and Stop global/shared service Sub-task Resolved Sandhya_Kripalani  
Tags: ee7_cleanup_closed

 Description   

Support association to different types of Services:

The Orchestrator must support binding of an application to the following types of Services:

  • External services(these are not provisioned by the orchestrator, but created and managed by an external user. Their lifecycle is not tied to an application and is not managed by the orchestrator. This is useful in scenarios where a user has existing DB/MoM investments and they want to reuse their existing setup for their application.)
  • Global/shared services (Services that are created by a DAS administrator that are provisioned and managed by the orchestrator. These services can be shared by multiple applications in the domain and the service lifecycle is not tied to a single application. This type of service is useful, for example, when multiple applications in a domain want to share the same database.)
  • Application-scoped services (These are services that are automatically provisioned by the orchestrator during PaaS-style deployment of the application, and their life-cycle is tied to the application's lifecycle.)


 Comments   
Comment by shreedhar_ganapathy [ 27/Oct/11 ]

Changed AffectsVersion to 4.0

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-16402] Single-click application provisioning and deployment of a PaaS application Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: 4.0_b61

Type: New Feature Priority: Blocker
Reporter: Sivakumar Thyagarajan Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-16403 Support External, Shared Provisioned ... Closed
depends on GLASSFISH-16404 Define deployment-time service metada... Closed
depends on GLASSFISH-16405 Automatically provision services duri... Closed
depends on GLASSFISH-16407 Automatic Service association for a P... Closed
depends on GLASSFISH-16410 Provide a set of standard pre-built S... Closed
depends on GLASSFISH-16411 Add administration and management cap... Closed
depends on GLASSFISH-16408 Service provisioning to support a sta... Closed
depends on GLASSFISH-16409 Support various PaaS deployment scena... Closed
Tags: ee7_cleanup_closed

 Description   

This is the umbrella RFE for the Service Orchestration feature in GlassFish 3.2.

Single-click application provisioning and deployment of a PaaS application through service dependency discovery, service provisioning and service association.



 Comments   
Comment by Sivakumar Thyagarajan [ 21/Apr/11 ]

Adding sub-RFEs for this umbrella RFE.

Comment by shreedhar_ganapathy [ 27/Oct/11 ]

Changed AffectsVersion to 4.0

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-16411] Add administration and management capabilities to support PaaS deployment Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: 4.0_b55

Type: New Feature Priority: Blocker
Reporter: Sivakumar Thyagarajan Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16402 Single-click application provisioning... Closed
Tags: ee7_cleanup_closed

 Description   

Add administration and management capabilities to support PaaS deployment:

  • P1: Admin command interception for managed services/resources: All the administration operations/commands on a managed entity(such as a cluster provisioned by the orchestrator) must be intercepted by the Orchestrator. The orchestrator will decide whether to allow or disallow these operations. (For example, orchestrator might not allow 'asadmin stop-cluster' on a managed cluster). Moreover, orchestrator might need to perform some additional tasks (eg: for book-keeping purposes) during the command execution on a managed object. Admin Infrastructure must wrap all the commands on the managed object to go to Orchestrator first.
  • P1: Additional asadmin commands: Implement admin commands for create/delete/list global services in a domain. The command implementation will internally invoke the plugin to do the needful. Plugin might internally use IaaS APIs, various existing glassfish commands to perform the task. Implement admin command to import/provision an external service into a domain.
  • P1: CLI/GUI to show all provisioned/shared services for a particular deployed application: Orchestrator, with the help of plugins can determine implicit service requirements or use default service requirements or use shared services in order to satisfy an application's various service requirements. There needs to be an administrative interface (eg: CLI) to show the list of all services used by a particular application. eg: The State of the service(started/stopped/stopping/starting) can also be shown. In case of partial undeployments, some services might be in deleted state.
  • P1: CLI/GUI to show the list of managed applications that share a particular services: A CLI command to list all applications that use or is bound to a global/shared service or an external service.
  • P2: Logging Orchestrator actions to aid troubleshooting: Since a PaaS-style deployment would entail a lot of Orchestrator operations (such as Template Matching, Service Provisioning, Service Assocation), it is imperative that the Orchestrator logs all its actions to enable offline troubleshooting.
  • P3: Monitoring probes: Expose monitoring probes for various Orchestrator functionalities
  • P3: Health check - service: Ability to perform a health-check on a particular Service (eg: ping)
  • P1: GUI (admin console) requirements: For example, a GUI option for PaaS style deployments, creating and registering Service Templates are suggested requirements on the admin console.


 Comments   
Comment by shreedhar_ganapathy [ 27/Oct/11 ]

Changed AffectsVersion to 4.0

Comment by shreedhar_ganapathy [ 07/Nov/11 ]

Need to revisit this issue to determine actual completion of several tasks listed in the description.
Siva, could you update the latest status of this RFE?

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-16410] Provide a set of standard pre-built Service Templates Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: paas-console, service-orchestration
Affects Version/s: 4.0
Fix Version/s: 4.0_b55

Type: New Feature Priority: Blocker
Reporter: Sivakumar Thyagarajan Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16402 Single-click application provisioning... Closed
Tags: ee7_cleanup_closed

 Description   

GlassFish 4 would come with standard pre-built templates for the supported service providers.

The orchestrator matches the service requirements of an application to a service template(either pre-built or user-provided) through its cloud metadata. The orchestrator/service plugin must not assume that the pre-built service template is the only template that could be provisioned. In other words, the orchestrator/plugin must support user-defined service templates.



 Comments   
Comment by shreedhar_ganapathy [ 27/Oct/11 ]

Changed AffectsVersion to 4.0

Comment by shreedhar_ganapathy [ 07/Nov/11 ]

I guess, this fix that went in as part of erstwhile 3.2 only partly addresses this requirement and additionally imposes an implicit requirement on PaaS console.
Updated components to reflect this.

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





Support External, Shared Provisioned and Application-Scoped Provisioned Services (GLASSFISH-16403)

[GLASSFISH-17584] allow provisioning of shared services without real application deployment Created: 03/Nov/11  Updated: 07/Feb/13  Resolved: 07/Feb/13

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: Sub-task Priority: Blocker
Reporter: Jagadish Assignee: Jagadish
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Shared services, when supported should provide an option/capability such that the services are provisioned even when no application is using the service.

eg:
create-shared-service command should provision (bring up a VM) a service that can be used by any applications that will be deployed later.



 Comments   
Comment by Tom Mueller [ 07/Feb/13 ]

The service orchestration code has been moved out of GlassFish, so closing this issue.





[GLASSFISH-17587] support atomic deployment of application Created: 03/Nov/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: New Feature Priority: Critical
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-17949 introduce various phases and tasks fo... Sub-task Closed Jagadish  
Tags: ee7_cleanup_closed

 Description   

Orchestration Engine should support atomic deployment of application
ie., either all necessary services are created, services are associated, application are deployed successfully.

This involves supporting atomic deployment in each of the phases

  • service discovery
  • provisioning
  • deployment
  • association

Atomic provisioning involves support from Orchestrator as well individual service provisioning engines.
[Sub tasks will be created for service provisioning engines.]



 Comments   
Comment by shreedhar_ganapathy [ 07/Nov/11 ]

This feature needs to be discussed at the arch meetings in terms of the lifecycle behavior in each phase - the failure modes in any one or more phase should not result in user having to do a long running deployment action. Perhaps a viable definition of atomic and sub-atomic operations needs to be done so recovery from a failure mode is defined and hence the operational behavior more predictable.

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-17594] API cleanup/refactoring in OE and SPE Created: 03/Nov/11  Updated: 07/Feb/13  Resolved: 07/Feb/13

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: Task Priority: Critical
Reporter: Jagadish Assignee: Jagadish
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

API cleanup/refactoring (Handling error conditions, failure scenarios in OE and SPEs)



 Comments   
Comment by Tom Mueller [ 07/Feb/13 ]

The service orchestration code has been moved out of GlassFish, so closing this issue.





[GLASSFISH-17590] design changes in OE w.r.t any change in architecture Created: 03/Nov/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: New Feature Priority: Critical
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-17599 Understand the new architecture and i... Sub-task Closed Jagadish  
GLASSFISH-17600 Functional Specification on new OE/SP... Sub-task Closed Jagadish  
Tags: ee7_cleanup_closed

 Description   

Umbrella RFE to capture any design changes required in OE in order to accommodate any architectural changes.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-17591] asynchronous deployment related support from OE Created: 03/Nov/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: New Feature Priority: Critical
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on GLASSFISH-12032 DYREC-007: progress status design Resolved
Tags: ee7_cleanup_closed

 Description   

Support from Orchestration Engine (with the help of SPEs) is required in order to support asynchronous deployment of PaaS styled applications.
This RFE will depend on overall asynchronous deployment or asynchronous command execution capabilities.



 Comments   
Comment by Jagadish [ 15/Nov/11 ]

Refer : http://wikis.sun.com/display/GlassFish/3.2ProgressDesign
for overall admin level feature.

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-17588] provide event listener mechanism so that SPEs can provide service state related information to the OE. Created: 03/Nov/11  Updated: 07/Feb/13  Resolved: 07/Feb/13

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: Task Priority: Critical
Reporter: Jagadish Assignee: Jagadish
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Define an API such that SPEs can use the event notification mechanism to notify the Orchestration Engine about various service states
eg: Started, Starting, Provisioning, Provisioned, Stopping, Stopped, Destroying etc.,



 Comments   
Comment by Tom Mueller [ 07/Feb/13 ]

The service orchestration code has been moved out of GlassFish, so closing this issue.





[GLASSFISH-18630] Early initialization of orchestrator components Created: 16/Apr/12  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0_b31
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Sanjeeb Sahoo Assignee: shreedhar_ganapathy
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-18293 virtualization modules are always active Closed
Tags: ee7_cleanup_closed

 Description   

From the following email response from Jagadish, it seems to me that we should be able to avoid early initialization of orchestrator component, so creating this bug...
---------
On Sat, 2012-04-14 at 13:15 +0530, Sahoo wrote:
> > I noticed Orchestrator being a PostStartup, but didn't look into the
> > reason. Why does it have to be a post startup service? Does it do any
> > background processing? What does it do after acquiring those services?
This is for initialization of all references w.r.t application, shared
services, external services etc.,
This is the book keeping information that will be used to act on a
particular service whenever some one wants to use the service (eg: CEM,
starting / stopping service / enabling/disabling application and all its
application scoped services etc.,).
I know what you will be asking me (to do) next

Thanks,
-Jagadish
-----------



 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-16408] Service provisioning to support a standard list of ServiceTypes and Service Providers Created: 21/Apr/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: 4.0_b55

Type: New Feature Priority: Major
Reporter: Sivakumar Thyagarajan Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16402 Single-click application provisioning... Closed
Tags: ee7_cleanup_closed

 Description   

Supported list of ServiceTypes and Service Providers

Support a standard list of service types and a list of service providers per ServiceType:
Suggested list:
RDBMS(JavaDB, MySQL)
HTTPLoadBalancer (TBD)
JMS(OpenMQ)



 Comments   
Comment by shreedhar_ganapathy [ 27/Oct/11 ]

Changed AffectsVersion to 4.0

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





Multiple DB plugins/templates in CPAS support (GLASSFISH-17560)

[GLASSFISH-17782] Orchestrator should provide a mechanism for defining default plugin Created: 21/Nov/11  Updated: 07/Feb/13  Resolved: 07/Feb/13

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: Sub-task Priority: Major
Reporter: Shalini Assignee: Sivakumar Thyagarajan
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

When there are are multiple service plugins for the same service type, the Orchestrator should provide a way to designate the default service plugin.



 Comments   
Comment by Tom Mueller [ 07/Feb/13 ]

The service orchestration code has been moved out of GlassFish, so closing this issue.





[GLASSFISH-17877] Native : Deployment of multiple apps fails in Native mode. Created: 01/Dec/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: shariffking Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

NA


Tags: ee7_cleanup_closed

 Description   

Steps to Reproduce
====================
1) Download glassfish 4.0 build 12 and extract.
2) Follow the steps for Native Mode for creating ims-config-native and create-template and copying the lb.zip etc.
3) Now deploy any app. Ex: Conference_Planner
4) Deployment is success and able to access the deployed app through load balancer URL.
5) Now deploy second app . Ex: basic_db_paas_sample (or) basic_paas_sample .
6) Deployment fails with the following error :
emote failure: Error occurred during deployment: Exception while invoking the lifecycle interceptor : Failure while deploying application [ basic_db_paas_sample ], rolled back all operations. Refer root cause – org.glassfish.paas.orchestrator.PaaSDeploymentException: Failure while provisioning services. Please see server.log for more details

7) If i reverse the order of deployed apps (i.e first basic_db and then conference planner) also the second app deployment fails.

server.log shows the following exception :
=============================================
[#|2011-12-01T13:02:06.671+0530|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=12;_ThreadName=Thread-2;|Failure while deploying application [ basic_db_paas_sample ], rolled back all operations. Refer root cause – org.glassfish.paas.orchestrator.PaaSDeploymentException: Failure while provisioning services
org.glassfish.deployment.common.DeploymentException: Failure while deploying application [ basic_db_paas_sample ], rolled back all operations. Refer root cause – org.glassfish.paas.orchestrator.PaaSDeploymentException: Failure while provisioning services
at org.glassfish.paas.orchestrator.state.ProvisioningState.handle(ProvisioningState.java:84)
at org.glassfish.paas.orchestrator.ServiceOrchestratorImpl.orchestrateTask(ServiceOrchestratorImpl.java:194)
at org.glassfish.paas.orchestrator.ServiceOrchestratorImpl.provisionServicesForApplication(ServiceOrchestratorImpl.java:253)
at org.glassfish.paas.orchestrator.ServiceOrchestratorImpl.preDeploy(ServiceOrchestratorImpl.java:502)
at org.glassfish.paas.orchestrator.ApplicationLifecycleInterceptorImpl$1.run(ApplicationLifecycleInterceptorImpl.java:102)
at org.glassfish.api.admin.AdminCommandLock.runWithSuspendedLock(AdminCommandLock.java:610)
at org.glassfish.paas.orchestrator.ApplicationLifecycleInterceptorImpl.before(ApplicationLifecycleInterceptorImpl.java:95)
at com.sun.enterprise.v3.server.ApplicationLifecycle.notifyLifecycleInterceptorsBefore(ApplicationLifecycle.java:570)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:421)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:249)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:411)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:351)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:366)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1076)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:98)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1309)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1277)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:479)
at com.sun.enterprise.v3.admin.AdminAdapter.onMissingResource(AdminAdapter.java:223)
at org.glassfish.grizzly.http.server.StaticHttpHandler.service(StaticHttpHandler.java:183)
at com.sun.enterprise.v3.server.HK2Dispatcher.dispatch(HK2Dispatcher.java:113)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:236)
at org.glassfish.grizzly.http.server.HttpHandler.doHandle(HttpHandler.java:163)
at org.glassfish.grizzly.http.server.HttpServerFilter.handleRead(HttpServerFilter.java:161)
at org.glassfish.grizzly.filterchain.ExecutorResolver$9.execute(ExecutorResolver.java:119)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeFilter(DefaultFilterChain.java:286)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.executeChainPart(DefaultFilterChain.java:223)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.execute(DefaultFilterChain.java:155)
at org.glassfish.grizzly.filterchain.DefaultFilterChain.process(DefaultFilterChain.java:134)
at org.glassfish.grizzly.ProcessorExecutor.execute(ProcessorExecutor.java:78)
at org.glassfish.grizzly.nio.transport.TCPNIOTransport.fireIOEvent(TCPNIOTransport.java:829)
at org.glassfish.grizzly.strategies.AbstractIOStrategy.fireIOEvent(AbstractIOStrategy.java:103)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.run0(WorkerThreadIOStrategy.java:111)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy.access$100(WorkerThreadIOStrategy.java:55)
at org.glassfish.grizzly.strategies.WorkerThreadIOStrategy$WorkerThreadRunnable.run(WorkerThreadIOStrategy.java:131)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:508)
at org.glassfish.grizzly.threadpool.AbstractThreadPool$Worker.run(AbstractThreadPool.java:488)
at java.lang.Thread.run(Thread.java:662)

#]

=============================================



 Comments   
Comment by Hong Zhang [ 01/Dec/11 ]

assign to jagadish for initial evaluation

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-17853] support multiple plugins (SPEs) of same type Created: 30/Nov/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: 4.0

Type: Bug Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-17875 Create config support for Service Pro... Sub-task Resolved Sandhya_Kripalani  
GLASSFISH-17876 Create CLI support for Service Provis... Sub-task Resolved Sandhya_Kripalani  
GLASSFISH-17948 backend support for multiple SPEs Sub-task Resolved Jagadish  
GLASSFISH-18154 Test case for register-service-provis... Sub-task Resolved Sandhya_Kripalani  
Tags: ee7_cleanup_closed

 Description   

Raising this feature request to support multiple service-provisioning-engines (SPEs) of same type (eg: Database).

Support involves :

  • Orchestrator to determine the set of SPEs that are of same type.
  • Resolve the conflict by referring domain.xml configuration for default SPE for a particular type.
  • Configuration for <service-provisioning-engines> and <service-provisioning-engine>
  • CLIs to register-spe, unregister-spe and list-spes.
  • Orchestrator to filter the SPEs and use them in the effective list of SPEs for deploying the application.


 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-17644] PaaS runtime should be extensible and should not be restricted to known service types Created: 04/Nov/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: iaas, paas-console, service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Bhavanishankar Assignee: Bhavanishankar
Resolution: Invalid Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified
Environment:

ALL


Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-17645 virtualization layer should not be re... Sub-task Closed shreedhar_ganapathy  
Tags: ee7_cleanup_closed

 Description   

Neither the orchestrator nor the IMS layer should restrict themselves to known service types viz., JavaEE, MQ, LB, DB.

Also, the GlassFish SPE should consider dynamically integrating GlassFish service with any newly added service. For example, Java EE PaaS application might want to use a third party HA store. GlassFish SPE should provide mechanism to augment such additional services.



 Comments   
Comment by shreedhar_ganapathy [ 07/Nov/11 ]

Added candidate components that will be impacted by this task.

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-17639] Run PaaS applications across multiple nodes in Native and KVM virtualization Created: 04/Nov/11  Updated: 07/Feb/13  Resolved: 07/Feb/13

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: Task Priority: Major
Reporter: Bhavanishankar Assignee: shamant
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Native and KVM virtualization



 Description   

Although the Native and KVM is mainly used for developer environment with single machine, it is necessary to ensure that service provisioning can scale across multiple nodes with Native/KVM virtualizations.

IMS seems to have support for this already. But PaaS application testing is currently limited only to single machine in Native & KVM environments.

As part of this task, run the PaaS tests by creating multiple server-pools with both local and remote nodes.



 Comments   
Comment by Tom Mueller [ 07/Feb/13 ]

The service orchestration code has been moved out of GlassFish, so closing this issue.





[GLASSFISH-17614] Revisit Plugin SPI and add better exception handling mechanism Created: 03/Nov/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Bhavanishankar Assignee: Sivakumar Thyagarajan
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ANY


Tags: ee7_cleanup_closed

 Description   

Plugin is currently missing a checked exception. Create one and use it wherever appropriate.

Also refine SPIs wrt remote Orchestration Engine.

Currently SPEs update the domain.xml directly. But updating domain.xml should not be done by the SPE implementations. Instead, the Orchestrator should take care of updating domain.xml using the ProvisionedService (or provisioning events) returned by the SPE.

IMS layer also should also throw the appropriate exception message to the upper level consumers like SPEs. Currently all IMS errors are abstracted as "unable to allocate virtual machine using any server pool" without much details. It is hard to find out the real cause.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-17601] Shared load-balancer service Created: 03/Nov/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: load_balancer, Service Provisioning Engine , service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: kshitiz_saxena Assignee: kshitiz_saxena
Resolution: Invalid Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-17602 Virtual server configuration for Apac... Sub-task Closed kshitiz_saxena  
GLASSFISH-17603 Virtual server configuration for OTD Sub-task Closed kshitiz_saxena  
Tags: ee7_cleanup_closed

 Description   

Need to support shared load-balancer service.



 Comments   
Comment by shreedhar_ganapathy [ 07/Nov/11 ]

Added candidate components that will be impacted by this task.

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





design changes in OE w.r.t any change in architecture (GLASSFISH-17590)

[GLASSFISH-17599] Understand the new architecture and its requirements on Orchestrator and SPEs Created: 03/Nov/11  Updated: 07/Feb/13  Resolved: 07/Feb/13

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: Sub-task Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Understand the new architecture and its requirements on Orchestrator and SPEs.



 Comments   
Comment by Tom Mueller [ 07/Feb/13 ]

The service orchestration code has been moved out of GlassFish, so closing this issue.





[GLASSFISH-17592] support redeployment of PaaS styled application Created: 03/Nov/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: deployment, paas-console, Service Provisioning Engine , service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed

 Description   

Need support to redeploy PaaS styled application.
Multiple factors need to be considered :
1) redeploy the application by re-provisioning the services as per the new service-requirements
2) redeploy the application by retaining (not re-provisioning) the services eg: via "asadmin redeploy --retainvm"
3) Need to find compatible and incompatible redeployment w.r.t services already available (for --retainvm) and accept or fail deployment.



 Comments   
Comment by shreedhar_ganapathy [ 07/Nov/11 ]

Added candidate components that will be impacted by this task.

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-17589] Better logging in Orchestrator Created: 03/Nov/11  Updated: 07/Feb/13  Resolved: 07/Feb/13

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: Task Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Provide better logging support in Orchestrator to make provisioning steps clearer.



 Comments   
Comment by Tom Mueller [ 07/Feb/13 ]

The service orchestration code has been moved out of GlassFish, so closing this issue.





[GLASSFISH-18434] Need event notification mechanism for a service Created: 01/Mar/12  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed

 Description   

Elasticity module has a requirement to send events to any provisioned service that is running in a PaaS runtime.
Following is the use-case from Mahesh :
"CEM to send a message / event to a service. Are there any APIs in OE/SPE that allows CEM to publish an event? There should be a way for the service instance (for example, GF instance) to receive a callback when an event arrives. One approach is to provide a plugin extension that uses GMS / Coherence to send events to JavaEE service instances"
And
MQ team also wants similar event mechanism :
"Could the CEM be used to send load information from an MQ JVM to the JVM that hosts an MDB, so the MDB can consider adding threads?"

We can introduce an event notification mechanism so that any service can be notified.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-18215] Abililty to turn of atomic deployment Created: 19/Jan/12  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0_b19
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed

 Description   

Currently, application deployment (and services provisioning) happens in an atomic fashion.
For debugging purposes, it would be helpful if one could turn off atomic behavior. An undocumented/unsupported flag would be helpful.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-18214] ability to switch provisioning services in parallel or serial mode Created: 19/Jan/12  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0_b19
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed

 Description   

Need a flag (atleast an undocumented/unsupported) to switch on or off parallel/serial provisioning of services.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-18212] Support hierachical/clustered representation of services Created: 19/Jan/12  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0_b19
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed

 Description   

Currently, the "Service" interface does not represent the hierarchical / clustered service model.
ie., the ability to retrieve the hierarchy of services or child services of a service is not available.

Need this support so that the service related information can be persisted by Orchestration Engine in domain.xml (as of today) and in tenant's configuration store (later). This will also help to avoid the usage of "ServiceUtil" API exposed by OE to update/register/unregister service related information.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-18213] Remove usage of ServiceUtil in Plugins. Created: 19/Jan/12  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0_b19
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed

 Description   

Currently, OE exposes ServiceUtil to Plugins in order to update/register/unregister/retrieve the service related information.
This can be avoided in most of the cases and the service related information should be persisted by OE as part of Orchestration.

Also, plugins should be able to retrieve the Service related information via the ServicePlugin / Service / ProvisionedService/ConfiguredService contract itself instead of ServiceUtil.getServiceInfo.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-18321] support for optional service-reference in a PaaS enabled application Created: 04/Feb/12  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed

 Description   

Currently, a service-reference request must be satisfied a matching service-description from a plugin. If no plugin can satisfy a service-reference requirement, deployment will fail.
We can have a potential use-case where there can be optional service-references which need not be always satisfied.

Use-case from Kshitiz :
LB Service Plugin can request a service-reference on DNS service. DNS Service Plugin need not be always available in the runtime and LB plugin can function without DNS plugin support.

In order to support such a use-case, it is necessary to support optional service-reference which when not satisfied need not fail deployment.
An INFO message can be logged about the unavailability of service for the optional service-reference requirement.



 Comments   
Comment by Jagadish [ 04/Feb/12 ]

FIX INFORMATION :

svn log -v -r 52433
------------------------------------------------------------------------
r52433 | jr158900 | 2012-02-04 21:13:08 +0530 (Sat, 04 Feb 2012) | 6 lines
Changed paths:
M /trunk/main/nucleus/paas/orchestrator/src/main/java/org/glassfish/paas/orchestrator/service/metadata/ServiceReference.java
M /trunk/main/nucleus/paas/orchestrator/src/main/java/org/glassfish/paas/orchestrator/state/ServiceDependencyDiscoveryState.java

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-18013] Test cases to be added for different CLIs of ServiceOrchestrator Created: 15/Dec/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: None
Fix Version/s: 4.0

Type: Improvement Priority: Major
Reporter: Sandhya_Kripalani Assignee: Sandhya_Kripalani
Resolution: Invalid Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-18014 Test Case for CLI list-services command Sub-task Resolved Sandhya_Kripalani  
GLASSFISH-18031 Test case for CLIs of shared service Sub-task Resolved Sandhya_Kripalani  
GLASSFISH-18089 Modify the enable-disable PaaS test c... Sub-task Resolved Sandhya_Kripalani  
GLASSFISH-18106 Extracting enabling/disabling tests f... Sub-task Resolved Sandhya_Kripalani  
GLASSFISH-18242 Test case: basic service discovery CLIs Sub-task Resolved Sandhya_Kripalani  
GLASSFISH-18411 Test case: Lazy Initialisation of sha... Sub-task Resolved Sandhya_Kripalani  
GLASSFISH-18495 Test case : MQ as a shared service Sub-task Resolved Sandhya_Kripalani  
Tags: ee7_cleanup_closed

 Description   

There are currently different CLI commands in ServiceOrchestrator module.
These commands should be tested via automated test-cases.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-18237] associate/dissociate should be called only on the plugins that requested via service-reference Created: 23/Jan/12  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 4.0_b20
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed

 Description   

Currently, during deploy and undeploy operations of PaaS enabled application, associate/dissociate will be on all Plugins which might introduce the overhead of each plugin that need to filter the associate/dissociate call based on ServiceProvider, ServiceConsumer and Service-Reference. This could be avoided if OE can bookkeep the plugins that requested service-references and call associate/dissociate only on respective plugins.



 Comments   
Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-17407] Assertion of app service description fails when paas test cases are run. Created: 11/Oct/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: service-orchestration
Affects Version/s: 3.1.2_b01
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: shamant Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed

 Description   

When paas test cases are run in native mode,assertion of metadata fails.
From CLI the app deployment succeeds because by default java assertions are disabled.As a result this assertion of metadata has no bearing on it.However when we run paas test cases we use maven surefire plugin where assertion are enabled by default.As a result it fails with an assertion error.By disabling the assertions in pom.xml of test cases deploy happens and test cases are executed successfully.As of now we are using this workaround to run various paas related test cases.

Below is the exception:-

[#|2011-10-11T12:20:39.507+0530|SEVERE|44.0|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=10;_ThreadName=main;|java.lang.AssertionError
at org.glassfish.paas.orchestrator.ServiceOrchestratorImpl.assertMetadataComplete(ServiceOrchestratorImpl.java:676)
at org.glassfish.paas.orchestrator.ServiceOrchestratorImpl.serviceDependencyDiscovery(ServiceOrchestratorImpl.java:357)
at org.glassfish.paas.orchestrator.ServiceOrchestratorImpl.provisionServicesForApplication(ServiceOrchestratorImpl.java:153)
at org.glassfish.paas.orchestrator.ServiceOrchestratorImpl.access$200(ServiceOrchestratorImpl.java:91)
at org.glassfish.paas.orchestrator.ServiceOrchestratorImpl$3.run(ServiceOrchestratorImpl.java:693)
at org.glassfish.api.admin.AdminCommandLock.runWithSuspendedLock(AdminCommandLock.java:610)
at org.glassfish.paas.orchestrator.ServiceOrchestratorImpl.before(ServiceOrchestratorImpl.java:686)
at com.sun.enterprise.v3.server.ApplicationLifecycle.notifyLifecycleInterceptorsBefore(ApplicationLifecycle.java:570)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:421)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:249)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:395)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:351)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:366)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1076)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:98)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1308)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1276)
at com.sun.enterprise.admin.cli.embeddable.DeployerImpl.deploy(DeployerImpl.java:129)
at org.glassfish.tests.paas.basicdbinitsql.BasicDBInitSqlTest.test(BasicDBInitSqlTest.java:97)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:66)
at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35)
at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)

To reproduce the issue:-
Remove the below line from pom.xml of any of the test cases residing in main/appserver/tests/paas/.e.g:it could be basic,basic-db,bookstore

"<enableAssertions>false</enableAssertions>"
This will enable the assertion and the above exception will be thrown when test cases are run.



 Comments   
Comment by shamant [ 18/Oct/11 ]

Changing assignee from sreedhar to jagdish

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





[GLASSFISH-17593] support undeployment of PaaS styled applications with --retainvm Created: 03/Nov/11  Updated: 01/Oct/12  Resolved: 01/Oct/12

Status: Closed
Project: glassfish
Component/s: iaas, paas-console, Service Provisioning Engine , service-orchestration
Affects Version/s: 4.0
Fix Version/s: None

Type: New Feature Priority: Minor
Reporter: Jagadish Assignee: Jagadish
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: ee7_cleanup_closed

 Description   

Need to support undeployment of application with --retainvm support so that VM and its data is retained.

Probably, this RFE might need support from SPEs and IaaS layer.



 Comments   
Comment by shreedhar_ganapathy [ 07/Nov/11 ]

Added candidate components that will be impacted by this task.

Comment by Tom Mueller [ 01/Oct/12 ]

Since cloud support has been removed from Java EE 7, this issue has been closed. This issue can be reopened if desired for future Java EE work.





Generated at Tue Aug 04 16:35:37 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.