Questions and Ideas #1
Comments
|
Johannes, I apologize for the delay in responding. I have been traveling this week. The broker-catalog.xml isn't configured in the master branch. It is Sizing is dependent on what your broker is doing. For example, if you are As for organizations, I honestly have not thought about creating a services Thanks for reaching out and getting involved. I would like to merge your Best, On Thu, Feb 13, 2014 at 7:15 AM, Johannes Hiemer
|
|
Hi Steve, Regarding the sizes I was asking, because I have only a small deployment environment on Openstack, which has no really heavy load. So there is no experience on my side. My thoughts were quite similar to yours. I think in most cases it is also a matter of experience. Perhaps some developments like the scaler would help here as well: https://github.com/nttlabs/bosh-scaler/blob/master/config/sample.yml I pushed to commits with Java Config for the default template and the MongoDB branch. You might take look on it. If you want, I would to highly appreciate to commit a pull-req and add value to the community. Perhaps what might be interesting for your as well is: It is build on the same stack. Spring 4 MVC with pure Java Config and in the frontend AngularJS. Honestly displaying services in this UI was the reason I stumbled over your blog entry. :-) An Idea I had here was for the admin part, to integrate the management of existing services, plans, tags etc. via UI. That's something I will be working on this weekend. Wish you a nice weekend, |
|
Hi Steve, I added the logging/mongodb as a service to my service organisation. Afterwards I had to do a Afterwards I tried to do a:
As an error was thrown, I traced the output (minor relevant output is removed, due to more readability): What makes we wonder here is the request body with: {"name":"logging-ad5da","service_plan_guid":"60694318-40a6-496a-b58d-b940b39a26fa","space_guid":"541ad3a1-d46e-493a-9423-f90ac98a8dc8"}to I checked the guids and all the stuff. Nothing seems wrong here, but as you can see I still get 403 forbidden. Is there still something I am doing wrong? |
|
@spgreenberg still out there? :-) |
|
I have been watching the bosh-scaler project anxiously as well. It looks I would be happy to incorporate a pull request. I am hoping more people I really like the idea of managing services (or even just having Any reason you implemented a maven build? Just curious more than anything. On Sat, Feb 15, 2014 at 4:25 AM, Johannes Hiemer
|
|
Unfortunately, the CURL request is a necessary hack. It is documented, but As for the error, I have a few questions: how did you register the broker? I took a look on github and didn't see a "logging" broker code base. I On Sun, Feb 16, 2014 at 5:54 AM, Johannes Hiemer
|
|
I am using maven due to the fact that I had not time yet to work with gradle. :-)
During the weekend I will have some time to make a pull request with Java config.
That would be really great, because it is not really good documented currently.
cf push --path=target/ssbt.war
....
cf add-service-broker log
URL> http://logging.192.168.1.222.xip.io
Username> admin
Password> cloudfoundry
Adding service broker log... OK
cf -v
cf 5.4.5
Log looks good so far.
https://github.com/jhiemer/cf-spring-service-broker Thanks a lot for your response! :-) |
|
cf v5.4.5 is the client CLI (command line interface). cf-release is the FYI - the ruby version of cf CLI (5.x) has been deprecated in favor of the On Thu, Feb 20, 2014 at 1:43 AM, Johannes Hiemer
|
|
I deployed your code to cf-release 158 on bosh lite and see the same issue. Sent from my iPhone On Feb 20, 2014, at 3:48 AM, Johannes Hiemer [email protected] I am using maven due to the fact that I had not time yet to work with I would be happy to incorporate a pull request. I am hoping more people can During the weekend I will have some time to make a pull request with Java Unfortunately, the CURL request is a necessary hack. It is documented, but That would be really great, because it is not really good documented how did you register the broker? Are you sure you have the correct username cf push --path=target/ssbt.war cf add-service-broker log Username> admin Password> cloudfoundry Adding service broker log... OK What version of cf-release are you using? cf -v If so, can you see anything in the logs? Log looks good so far. cf logs logging Reading logs/env.log... OK Reading logs/staging_task.log... OK Reading logs/stderr.log... OK
Reading logs/stdout.log... OK I took a look on github and didn't see a "logging" broker code base. https://github.com/jhiemer/cf-spring-service-broker Thanks a lot for your response! :-) Reply to this email directly or view it on |
|
I am on my way to migration to CF CLI v6 atm. Just waiting for a response on the brew tab reliability. I saw that you forked cfmc. It did a larger refactoring using pure and native Jackson support, which increases the speed, when loading the resources and removed the boilerplate repositories. You should delete your fork and refork the current version. Maybe we could work together on it. What do you think? Sadly I have a small issue here with my VPN, so I am not able to get into our CF Demo lab. Going to install the Lite version in a VM now, for further testing later on. |
|
@spgreenberg I figured it out. The reason was the following line: CustomSecurityConfiguration.java @Override
protected void configure(HttpSecurity http) throws Exception {
http
.authorizeRequests()
.antMatchers("/**").hasRole("USER")
.anyRequest().authenticated()
.and()
.httpBasic()
.and()
.csrf().disable();
}Had to add Thanks a lot for your help! Btw. in my opinion the new CF client is a huge step backwards. cf push APP [-b BUILDPACK_NAME] [-c COMMAND] [-d DOMAIN] [-f MANIFEST_PATH]
[-i NUM_INSTANCES] [-m MEMORY] [-n HOST] [-p PATH] [-s STACK] [-t TIMEOUT]
[--no-hostname] [--no-manifest] [--no-route] [--no-start]Is there any way to shorten that, or have the dialogs, we had in the previous ruby client? |
|
Hi, |
|
@sreelathakoye as it is a normal Spring app it should work. Could you get the logs via cf logs yourappnameAnd the contents of the files in |
|
I would also point you to the new spring-boot version rather than the Spring boot makes composing apps from different spring technologies I am not planning on supporting/updating the spring-service-broker, instead On Thu, May 8, 2014 at 8:24 AM, Johannes Hiemer [email protected]:
|
|
Thank you @spgreenberg and @jhiemer , very sorry for the late reply, i would try working on Spring-boot project links which you have provided |
First of all, thanks a lot for this nice sample. Regarding your implementation I have a few questions about the code itself and in general:
What do you recommend regarding size and number of instances for a broker? Is it best practice to put them into a separate organisation (e.g. services) and then conclude those into different spaces (e.g. logging, queuing, sql...) etc.?
The text was updated successfully, but these errors were encountered: