Hi Nipun, Did you change the database and develop related JPA layer and resource layer. By looking at the error, the reason could be you forgot to add that class to the persistence.xml inside airavata/modules/app-catalog/app-catalog-data/src/main/resources/META-INF/persistence.xml. When you add a new JPA model class, you need to add it in the persistence.xml too.
On Thu, Aug 7, 2014 at 2:31 AM, Nipun Udara <[email protected]> wrote: > Hi Lahiru > > CloudJobSubmission jobSubmission=new CloudJobSubmission(); > jobSubmission.setExecutableType("sh"); > jobSubmission.setProviderName(ProviderName.EC2); > jobSubmission.setSecurityProtocol(SecurityProtocol.SSH_KEYS); > jobSubmission.setNodeId("i-3040241c"); > jobSubmission.setUserAccountName("ec2-user"); > > client.addCloudJobSubmissionDetails(host.getComputeResourceId(),1,jobSubmission); > > When i try to add cloudSubmission i got a error as below. any idea about > this. > > AiravataSystemException(airavataErrorType:INTERNAL_ERROR, message:Error > while adding job submission interface to resource compute resource. More > info : org.airavata.appcatalog.cpi.AppCatalogException: > <openjpa-2.2.0-r422266:1244990 nonfatal user error> > org.apache.openjpa.persistence.ArgumentException: No metadata was found for > type "class > org.apache.aiaravata.application.catalog.data.model.CloudJobSubmission". > The class is not enhanced.) > at > org.apache.airavata.api.Airavata$addCloudJobSubmissionDetails_result$addCloudJobSubmissionDetails_resultStandardScheme.read(Airavata.java) > at > org.apache.airavata.api.Airavata$addCloudJobSubmissionDetails_result$addCloudJobSubmissionDetails_resultStandardScheme.read(Airavata.java) > at > org.apache.airavata.api.Airavata$addCloudJobSubmissionDetails_result.read(Airavata.java) > at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:78) > at > org.apache.airavata.api.Airavata$Client.recv_addCloudJobSubmissionDetails(Airavata.java:3040) > at > org.apache.airavata.api.Airavata$Client.addCloudJobSubmissionDetails(Airavata.java:3025) > at > org.apache.airavata.client.tools.DocumentCreatorNew.createEc2HostDocs(DocumentCreatorNew.java:148) > > > On Tue, Aug 5, 2014 at 3:02 PM, Nipun Udara <[email protected]> wrote: > >> Hi lahiru >> >> Thank you for adding this. i will have a look. >> >> Regards >> Nipun Udara >> >> >> On Tue, Aug 5, 2014 at 12:31 PM, Lahiru Gunathilake <[email protected]> >> wrote: >> >>> Hi Nipun, >>> >>> I have added new JobSubmission protocol called Cloud, please update the >>> trunk, Since you are waiting I committed without a sample. I will provide a >>> sample but I prefer you to try it out without waiting for my sample. If you >>> find any issues let me know. >>> >>> Lahiru >>> >>> >>> On Tue, Aug 5, 2014 at 7:29 AM, Lahiru Gunathilake <[email protected]> >>> wrote: >>> >>>> Hi Nipun, >>>> >>>> Please provide some more details about the following fields ? >>>> >>>> >>>> On Thu, Jul 31, 2014 at 7:45 AM, Nipun Udara <[email protected]> >>>> wrote: >>>> >>>>> Hi suresh >>>>> >>>>> Thanks for the feedback. These are things i need so far >>>>> >>>>> nodeId >>>>> executableLocation >>>>> ExecutableType >>>>> >>>> What are the possible values for this ? can I define this as an enum ? >>>> >>>>> workingDirectory >>>>> inputOutPutDirectories >>>>> StandardError and StandardOut Directories >>>>> CloudProvider name- for ec2 "aws-ec2" >>>>> >>>> What are the other enum values ? >>>> >>>>> user account name in Node - for ec2 - "ec2-user" >>>>> >>>> What are the possible values for this ? can I define this as an enum ? >>>> >>>>> >>>>> Perhaps all of these things can be saved with app-catalog already if >>>>> so please correct me. So far i have mainly focused on ec2. but clearly >>>>> with minimal effort we can used gfac provider with other jclouds >>>>> Providers. >>>>> if we take docker, the difference is creating the computingserviceContext, >>>>> the provider name and the security details. and other things will remain >>>>> same as long as the docker node is shell accessible. >>>>> >>>>> regards >>>>> Nipun Udara >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Thu, Jul 31, 2014 at 2:35 AM, Suresh Marru <[email protected]> >>>>> wrote: >>>>> >>>>>> Hi Nipun, >>>>>> >>>>>> Can you tell me what all information you will need to register EC2, >>>>>> Rackspace? Lets quickly add it instead of you reverting to a old code. >>>>>> >>>>>> Which all JClouds providers did you try from >>>>>> https://jclouds.apache.org/reference/providers/ ? >>>>>> >>>>>> Are you writing a generic JClouds GFac provider which will be easy to >>>>>> work with the above listed jClouds providers? Taking an example, lets say >>>>>> docker (https://jclouds.apache.org/guides/docker/), how much effort >>>>>> will be to modify your provider and docker support? >>>>>> >>>>>> Suresh >>>>>> >>>>>> On Jul 30, 2014, at 3:41 PM, Nipun Udara <[email protected]> >>>>>> wrote: >>>>>> >>>>>> > Hi all >>>>>> > >>>>>> > I have to test ec2 application registration with app catalog, and i >>>>>> have look at the BetterGFacImpl and seems app-catalog intergration doenot >>>>>> support ec2. >>>>>> > >>>>>> > So I would like to know whether i can continue rest of the work >>>>>> with the old code . >>>>>> > >>>>>> > regards >>>>>> > Nipun Udara >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Nipun Udara >>>>> >>>>> *Undergraduate* >>>>> *Department of Computer Science & Engineering* >>>>> *University of Moratuwa* >>>>> *Sri Lanka* >>>>> >>>>> >>>> >>>> >>>> -- >>>> System Analyst Programmer >>>> PTI Lab >>>> Indiana University >>>> >>> >>> >>> >>> -- >>> System Analyst Programmer >>> PTI Lab >>> Indiana University >>> >> >> >> >> -- >> Nipun Udara >> >> *Undergraduate* >> *Department of Computer Science & Engineering* >> *University of Moratuwa* >> *Sri Lanka* >> >> > > > -- > Nipun Udara > > *Undergraduate* > *Department of Computer Science & Engineering* > *University of Moratuwa* > *Sri Lanka* > >
