@imaffe I created this template for you to play with EFS easily. It creates three ASG's of 1 instance each, spread across different AZ's
it also creates and EFS with mount targets and a SG
this will allow you to play around with the scenarios we mentioned last night
You will need to a ssh keys to the launch configuration resource in the cloudformation template to enable ssh.
@hynespm Hi Patrick, I found that I might misunderstood your definition of a mount point in the previous meeting and my origin understanding of mount point should be correct after reviewing some materials : A mount point is not a thing on a file system, it is a directory under the host OS directory tree, and a file system mount its top-most inode to that directory, and we call that directory a mount point.
1.So I take this as, for one EFS, and one host OS, if you mount the EFS to 2 directory under the directory tree, say /mp1 and /mp2, you would see exactly the same thing under the two directories .
1.So I take this as, for one EFS, and one host OS, if you mount the EFS to 2 directory under the directory tree, say /mp1 and /mp2, you would see exactly the same thing under the two directories .
- btw, I still don't understand your multi-mount point scenario , can you show us using a diagram in next meeting ? I will also draw a diagram of my understanding of our project.
give me one minute...
- https://jenkins.io/projects/gsoc/students/#coding-periods
- Jira Issues: up to date
- Blog post by student on coding phase 1: reminded Yufei
- Ask questions on mailing list
- Push code everyday or almost every day.
- Announce the design document on mailing list , keep it up to date as questions are answered
@martinda @alexsomai @hynespm I have a UI related problem, and I might need some UI related knowledge transfer . The scenario is : in the global configuration page, and when user clicked
add Disk, there would be a disk type drop down box. And I want the entries different for every choice. e.g. if user choose efs disk, there would be 3 or 4 more fields coming out. I don't know how to do this, and is reviewing the tutorial video. If you can tell me where I can find the answers, I can just go there and learn by myself. Thanks ~ :)
Regarding the PRs, I think we have to decide how it would be better to proceed. Here is my proposal: Create a new branch in EWM from
master, and it could be named 2.0, or cloud-extension, or something like this. Then, Yufei, you could create all your PRs against this branch. When all the work is finished on the AWS - EFS support, only then do merge the entire cloud-extension branch into master. What do you guys think about this?
My concern is that everything that goes into
master should be ready for release
That is a standard git workflow.
+1
alright, so I've created this branch
cloud-aws-efs https://github.com/jenkinsci/external-workspace-manager-plugin/tree/cloud-aws-efs, and Yufei, you can create your PRs against this one. I'll find some time tomorrow to look over what you've raised so far, even if it's work in progress
@imaffe here is some documentation that might help you https://wiki.jenkins.io/display/JENKINS/Basic+guide+to+Jelly+usage+in+Jenkins
basically, you need to place the config.jelly file under the same directory structure as where it's placed the
Describable implementation
and some more documentation
and what I also did was to look at other plugins
yep, hope it helps
and, if you search for some jelly properties in the github jenkinsci, like this https://github.com/search?q=org%3Ajenkinsci+f%3ArepeatableHeteroProperty&type=Code
you can find many usages
oh, I don't think I did anything in Groovy (UI related)